Skip to content

A new command line option to force the creation of the next version of the component. #1018

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.

Sign up for GitHub

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

Jump to bottom
Closed
boocmp opened this issue Dec 4, 2024 · 0 comments · Fixed by #1019
Closed

A new command line option to force the creation of the next version of the component. #1018

boocmp opened this issue Dec 4, 2024 · 0 comments · Fixed by #1019
Assignees
@boocmp

Comments

@boocmp
Copy link
Contributor

boocmp commented Dec 4, 2024 •
edited
Loading

--force-next-version boolean parameter.

This option will allow you to create a new version of the component when the actual payload does not change. It can be useful when changing the properties of the CRX itself (publisher keys, crx headers, metadata).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@boocmp boocmp

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added --force-next-version command line param. brave/brave-core-crx-packager
1 participant
@boocmp