Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto-update version #20

Open
aaronczichon opened this issue May 8, 2024 · 1 comment · May be fixed by #43
Open

Auto-update version #20

aaronczichon opened this issue May 8, 2024 · 1 comment · May be fixed by #43
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@aaronczichon
Copy link
Owner

Description

Currently the version of the manifest.json file need to be set manually by the developer before making a release.

Expectation

It would be nice, if the release workflow makes a commit where the manifest.json version is updated and commited without triggering a new build and release.

@aaronczichon aaronczichon added the enhancement New feature or request label May 8, 2024
@aaronczichon aaronczichon added this to the 1.1.0 milestone May 8, 2024
@aaronczichon aaronczichon self-assigned this May 8, 2024
@aaronczichon aaronczichon modified the milestones: 1.1.0, 1.2.0 May 14, 2024
@aaronczichon aaronczichon modified the milestones: 1.3.0, 2.0.0 Aug 5, 2024
@aaronczichon
Copy link
Owner Author

Creating a new tag with a version should automatically update the version in the package.json and manifest.json. Commit it to the main branch and then creating a release.

aaronczichon added a commit that referenced this issue Oct 27, 2024
@aaronczichon aaronczichon linked a pull request Nov 21, 2024 that will close this issue
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant