docs: add versioning #305
Merged
docs: add versioning #305
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
|
Currently waiting for #300 to test both changes together in the release pipeline. |
|
katexochen
force-pushed
the
p/docs-release
branch
from
39b5b9e to
a118c3b
Compare
Signed-off-by: Paul Meyer <[email protected]>
Signed-off-by: Paul Meyer <[email protected]>
Signed-off-by: Paul Meyer <[email protected]>
katexochen
force-pushed
the
p/docs-release
branch
from
a118c3b to
39d7355
Compare
Signed-off-by: Paul Meyer <[email protected]>
Signed-off-by: Paul Meyer <[email protected]>
katexochen
force-pushed
the
p/docs-release
branch
from
39d7355 to
11bd283
Compare
|
Successful release workflow: https://github.com/edgelesssys/contrast/actions/runs/8611386270 |
|
Release PR for main: #308 |
katexochen
added
documentation
msanft
approved these changes
Apr 9, 2024
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.
Adding a step to the release pipeline to create a new docs version on the main branch. This way, docs will be versioned and users will be able to view docs of previous and latest version, while we can work on the docs of the next version without producing inconsistencies.