Skip to content

Document how to update ty's conformance results upstream#3028

Merged
AlexWaygood merged 2 commits intomainfrom
alex/conformance-updates
Mar 12, 2026
Merged

Document how to update ty's conformance results upstream#3028
AlexWaygood merged 2 commits intomainfrom
alex/conformance-updates

Conversation

@AlexWaygood
Copy link
Copy Markdown
Member

@AlexWaygood AlexWaygood commented Mar 12, 2026

We don't want to make this a mandatory part of the release process, because we don't want to make the release process more arduous than it is currently: easy, automated releases are a very good thing. But we should nonetheless document how to update these results, so that it's not information exclusively known to me :-)

@AlexWaygood AlexWaygood added the documentation Improvements or additions to documentation label Mar 12, 2026
@AlexWaygood AlexWaygood changed the title alex/conformance updates Document how to update ty's conformance results upstream Mar 12, 2026
@AlexWaygood AlexWaygood force-pushed the alex/conformance-updates branch from b38c600 to 919e7f0 Compare March 12, 2026 14:10
Comment thread CONTRIBUTING.md Outdated
@AlexWaygood AlexWaygood enabled auto-merge (squash) March 12, 2026 22:06
@AlexWaygood AlexWaygood merged commit 1adde13 into main Mar 12, 2026
13 checks passed
@AlexWaygood AlexWaygood deleted the alex/conformance-updates branch March 12, 2026 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants