Skip to content

Refine the lock coverage checker and capture the lock lesson (Refs #4753) - #4859

Merged
EHotwagner merged 1 commit into
mainfrom
routine/4753-lock-adoption-followup-20261024
Oct 24, 2026
Merged

EHotwagner merged 1 commit into
mainfrom
routine/4753-lock-adoption-followup-20261024

Conversation

@EHotwagner

Copy link
Copy Markdown
Contributor

Follow-up to #4858 (merged as c799a9f), found while preparing the producer adoption PRs.

  • git tag is no longer a publication token. Rendering's read-only plan job mentions git tag and git push inside a parsing pipeline, and a local tag publishes nothing; pushing a tag (git push --tags|refs/tags|--atomic) remains one. New controls cover both directions.
  • Rendering release-tags.yml plan is declared an observer in registry/publication-writers.json (it holds contents: read and cuts nothing).
  • One Atlas lesson, github/org-publication-writer-lock-job-name-marker: the Actions job step list is often empty, so lock participants are recognised by job name and server-side started_at. Both Atlas seeds and the driver manifest digests are regenerated; tests/atlas/check.py passes (393 records).

Inert to publication: no workflow in this repository changes. Refs #4753 #4730.
architecture-map: unaffected

🤖 Generated with Claude Code

… an observer and capture the lock lesson in Atlas (Refs #4753)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@EHotwagner
EHotwagner merged commit f36a11c into main Oct 24, 2026
61 checks passed
@EHotwagner
EHotwagner deleted the routine/4753-lock-adoption-followup-20261024 branch October 24, 2026 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant