Repository navigation
Gate deployment changes on a changelog entry, and pin what CI runs - #12
Merged
danielplohmann merged 1 commit intoSep 23, 2026
Merged
Conversation
This repository releases by moving the pins in .env and writing a dated CHANGELOG.md entry, and since the Keep a Changelog adoption its own changes have somewhere to go - but nothing made anyone write them down. A pull request that changes what a deployment is built from now has to touch CHANGELOG.md or carry the no-changelog label. RELEASING.md says how a bump is done, what a release is here, and where this repository sits in the ecosystem's release order. CI pins actions/checkout to a commit SHA, drops the checkout's credentials from the runner, and runs with a read-only token. Dependabot watches the pinned actions and the Ubuntu base images of both Dockerfiles, so a base image bump arrives as a reviewable change rather than as whatever the tag resolved to on rebuild day.
This was referenced Sep 12, 2026
Open
danielplohmann
approved these changes
Sep 23, 2026
danielplohmann
left a comment
Collaborator
There was a problem hiding this comment.
Approved. The no-changelog label now exists, so the gate has its escape hatch from the moment this lands.
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.
#11 adopted Keep a Changelog and gave this repository's own changes somewhere to go, and said why that mattered: the Dockerfile learning to install from
pyproject.toml,entry_test.shgaining pytest and the TUNING.md drift check had all landed without an entry. Nothing makes the next such change write one either.This is one of six pull requests giving the MCRIT ecosystem one release process. This repository is a deployment rather than a package — no version, no tag, no index — so it takes only the part that applies:
CHANGELOG.mdis the single authoritative record, written when a change merges, and CI enforces that.Changes
Changelogcheck: a pull request that changes what a deployment is built from —docker/,nginx/,config/, the compose files,.envor the helper scripts — has to touchCHANGELOG.mdor carry theno-changeloglabel. Read-only token, no PR content executed, Dependabot exempt.RELEASING.md: what a release is here (a merged bump of.envwith a dated entry), how a bump is done step by step, and where this repository sits in the ecosystem's release order (smda → MCRIT → MCRITweb → docker-mcrit).actions/checkout@v3(a floating major, two majors behind) is pinned to the v7.0.1 commit SHA withpersist-credentials: false, and the workflow runs withcontents: read.ubuntu:24.04base images of both Dockerfiles monthly, so a base-image bump arrives as a reviewable change.No change to the images, the compose files or the shipped config. Python 3.12 was already what the images run, which is the floor the rest of the ecosystem now shares.
Tests
actionlintandzizmor --persona=regularreport no findings on the workflows. The build-test job itself is untouched apart from the pin.What a maintainer has to configure once
no-changeloglabel.Related pull requests across the ecosystem
The same process, one PR per repository. None depends on another to merge; release order once merged is smda → purepdb → picblocks → MCRIT → MCRITweb → docker-mcrit.