Refactor release and publish action - #26
Merged
Merged
Conversation
biggusdonzus
force-pushed
the
ci/refactor-release-publish
branch
from
July 27, 2026 15:52
143497f to
c6d9de9
Compare
mromanelli9
approved these changes
Jul 28, 2026
biggusdonzus
force-pushed
the
ci/refactor-release-publish
branch
from
July 28, 2026 08:35
c6d9de9 to
6f95503
Compare
farnsworth
approved these changes
Jul 28, 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
3 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.
The pipeline is failing because of an issue with mkdocs, first look at: #27.
Remove the need to use a custom github PAT token, by running the publish code in the same action (but different job). Also the build-library and publish functionality was split into composite actions, that are reused from the
publish.ymlci pipelines (which is only a manual trigger).