Repository navigation
docs: publish the README screenshot with the demo, and write down the release rule - #38
Merged
Merged
Conversation
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.
Screenshot
The README screenshot was a fixed PNG in the repo, so it would go stale the next time the page changed. The Demo workflow now takes it from the demo it just built and publishes it as
https://modern-python.github.io/release-scope/screenshot.png, which the README now shows.docs/images/demo.pngis gone.demo/screenshot.pyopens the demo with SHOP-38 chosen and saves a 2x light-theme PNG.just demo-screenshotruns it and installs Chromium on first use.demo/server.pyholds the local static server that the smoke tests already used, so the screenshot script can share it.Until the workflow runs, the image at that URL does not exist. I'll trigger the workflow right after merging.
Release rule
AGENTS.mdnow says what tag history shows: every report schema bump (schemas 2 to 7, in 0.3.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, and 0.9.0) shipped as a new minor release, with the skill range and README pins moved in the same change. Anything else is a patch.