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.

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

bump version to 1.5.10 #465

Merged
merged 2 commits into from
Dec 11, 2024
Merged

bump version to 1.5.10 #465

merged 2 commits into from
Dec 11, 2024

Conversation

sentientforest
Copy link
Contributor

manually

@sentientforest
Copy link
Contributor Author

I'm not yet familiar enough with how our versioning Github actions are setup to know if they support auto-creating version bump commits for version 1.x now that we have released version 2.x.

...guessing that .github/workflows/manual-version-bump.yml is the workflow to trigger. Looks like maybe the versions in main-v1 and main are slightly different.

However it's easy enough to run node unifyVersions.js <new version number> and create a pull request to main-v1 manually, so I have done so here - it basically replicates what's in that workflow.

This should get approved and merge prior to publishing the next 1.5.x version, to properly increment the versions across package.json files.

@sentientforest sentientforest merged commit 93871b7 into GalaChain:main-v1 Dec 11, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dzikowski dzikowski dzikowski approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@sentientforest @dzikowski