chore(ci): bump release npm pub trusted updates#98
Conversation
Summary of ChangesHello @leet4tari, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request is a routine chore aimed at validating the project's npm publishing workflow. It involves incrementing the version numbers across all related Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the version numbers across several package.json files from 0.14.5 (or 0.14.4 for docusaurus/tari-docs) to 0.14.6. This change aligns with the pull request description, which indicates a bump for npm publishing tests and testing the current release process. The changes are purely metadata updates and appear to be in order for a version increment.
Description
bump release for npm publishing test
Motivation and Context
test current release process