Fix/release#2
Closed
zcstarr wants to merge 40 commits into
Closed
Conversation
This change add support for retrieving and applying release notes to the broader docs interface after creating a release through the github interface. This in turn creates a PR to merge that includes md documentation that tracks the release notes. This is part 1 of 2 commits to incrementally support multiversion releases.
… spec This is the second portion of a commit to release docs. We take tagged releases and then generate release notes that are then stored in docs release so they can be viewed from the documentaiton site. We also generate a snapshot of the documents so we can support multiple versions going back in time. Finally, we add support for next, which are so we can see changes that have been added to main but have not been released yet. This will make it easy to then understand the documentation. Additionally, we must have a follow up PR that adds the release notes to the doc site, as this is cleaner than needing to publish to update the release notes everytime. This will allow for one off typo changes that don't need to go through the release process from scratch but can just be committed into mainline.
Feat/release part1
fix: fix publish spec to be more resillent to release order and potne…
…ual publish if needed
fix: combine release and publish spec, and leave publish spec for man…
docs: release notes for v0.0.1
…sion number with 0.0.0
fix: resolves version writing issue where build:spec replaces the ver…
docs: release notes for v0.0.2
Prior to this change releases updating the website dependended on a subsequent commit to main to update the changes, where as now. We take the pending release update and make sure to add it to the api version so we capture updated values. This allows us to on publish have a proper deployed website with the right versions.
fix: changes fix awkward update release pattern.
docs: release notes for v0.0.3
fix: rename the workflows
docs: release notes for v0.0.4
fix: concurrency in deploy pages issue by cancelling deploy in progre…
docs: release notes for v0.0.5
chore: adjust banner to remove unmaintained warning
docs: release notes for v0.0.6
docs: release notes for v0.0.7
fix: banner status
docs: release notes for v0.0.8
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
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.
No description provided.