Repository navigation
Conversation
This branch has not been deployed
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.
Release tags pushed by the Package workflow use
GITHUB_TOKEN, so GitHub suppresses the tag-push event that would otherwise start documentation deployment. This left the v1.0.0 release without a docs run.After publishing to PyPI and successfully pushing a new release tag, explicitly dispatch
docs.yamlagainst that exact tag. Grantactions: writefor the dispatch and retain the existing version-bump condition and default success gating. Also quote$GITHUB_OUTPUTto resolve an existing ShellCheck finding in the modified workflow.Validation:
actionlint .github/workflows/main.yaml .github/workflows/docs.yamlpassed.pre-commit run --files .github/workflows/main.yamlpassed.git diff --checkpassed.No live release or docs deployment was triggered during validation. This change applies to future releases; it does not backfill v1.0.0.