Document how to make a release and use real version in apiService - #330
Merged
Conversation
Collaborator
Author
|
I realized that the apiService had "1.0" hardcoded. Added a commit to use the real PyHSS version there while at it, and adjusted the docs to now change it in |
osmith42
changed the title
Move the version number from pyproject.toml to lib.version.pyhss_version and display it in apiService's /docs/ site, instead of "1.0".
Takuto88
approved these changes
Aug 16, 2026
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.
As we are getting close to making a new release, I think it would be good to document the process.
@Takuto88: how about this?