Merged
Conversation
Contributor
jakep36
approved these changes
Apr 21, 2025
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
2 participants
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.
When tag is pushed it will push docker image to docker hub and create a github release with change log and link to the docker image. See https://github.com/fluree/server/releases
If the tag is on the main branch it should also update the fluree/server:latest tag if version number does not have a suffix so that it does not get updated for prerelease tags like v1.2-alpha or v1.2-experimentalfeature.
Also allows creating branch of older version such as release/v1.1 for support and maintenance of older releases if needed without erroneously updating latest (since these hotfixes may be backported from main but not on main)
After review and merge I'll tag as v1.0.0