Release 2.2.0#19
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Bumps the project version to 2.2.0 in npm metadata for the 2.2.0 release.
Changes:
- Update
package.jsonversion from2.1.2to2.2.0.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
| { | ||
| "name": "sequra-core-admin-fe", | ||
| "version": "2.1.2", | ||
| "version": "2.2.0", |
There was a problem hiding this comment.
question: The PR description mentions bumping both package.json and package-lock.json, but the reviewed diff only shows package.json. Should package-lock.json also be updated in this PR to keep lockfile metadata in sync with the release version?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the goal?
Bump version to 2.2.0 in package.json and package-lock.json
How is it going to be deployed?
Standard deployment