[TEST] Automate publishing and update versioning #257
Closed
Conversation
This file contains 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
The new versioning is described in the README. Add changelog and provide generic entry for 0.8.1. Update all components to version `0.9.0-next`.
The docker components will be build on PRs. The images will be published on main push as `version-next` and `version-next.sha` tags. If a release is published the images will be pushed as `latest` and `version` tags.
There are no separate next tags for each version for npm packages.
The same can be done for the docker builds, if successful.
sgraband
force-pushed
the
versioningUpdate
branch
2 times, most recently
from
53411b0 to
73c9ca2
Compare
sgraband
force-pushed
the
versioningUpdate
branch
from
73c9ca2 to
f6fe0d4
Compare
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.
This is just a test PR to test some CI functionalities.