Repository navigation
chore(release): date 0.10.0 - #57
Merged
Merged
Conversation
Releases wheelname.ParseTags (#56) so the PyPI manifest producer can consume it; rstudio/package-manager#20776 is blocked on this tag existing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Dates the accumulated
[Unreleased]section as0.10.0, sowheelname.ParseTags(#56) is consumable. rstudio/package-manager#20776 — the producer backfill pass that picks up the tags this recovers — is blocked on the tag existing.Additive only;
Parse's behaviour is unchanged. Minor bump, matching the repo's 0.7 / 0.8 / 0.9 history.[Unreleased]held only theParseTagsentry, and I checked its prose for staleness before dating rather than after: it cites measurements and filename examples, nothing time-sensitive. That check exists because the go-pyresolver 0.11.0 release earlier today had to correct a sentence that had gone false — a dated section cannot be revised once the module proxy has served the tag.go build,go vetclean;go test ./...green across all 12 packages.🤖 Generated with Claude Code