Stabilize publication infrastructure: scope detection guard, Pages fallback, release dedup, metadata corrections#182
Merged
Conversation
77 tasks
…, release dedup, metadata fixes, deliverables - S1: Add git cat-file reachability guard to publication.yml detect-scope, eliminating fatal: bad object failures on force-push/rebase/first push - S2: Fix .zenodo.json license from 'mit' to 'apache-2.0' (correct SPDX id) - S3: Fix docs/index.html hardcoded version from v0.0.1 to v0.1.1 - M1: Fix pages.yml synchronization and verification steps to gracefully handle missing docs/ PDFs when builds are skipped (warn + continue instead of hard fail) - M2: Add release-exists pre-check to release-paper.yml to prevent race condition with publication.yml release job - Generate audits/publication-infrastructure-audit-followup.md - Generate audits/publication-artifact-inventory.json - Generate docs/publication-workflow-map.md Co-authored-by: szmyty <14865041+szmyty@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Stabilize publication infrastructure and improve workflow reliability
Stabilize publication infrastructure: scope detection guard, Pages fallback, release dedup, metadata corrections
Jun 2, 2026
Pull Request Summary by devActivityMetricsAchievements
|
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.
Several compounding fragilities in the publication pipeline cause predictable failures under common conditions (force-push, docs-only commits, concurrent release triggers). This PR addresses the highest-impact issues identified in the publication system audit.
Workflow fixes
publication.yml— missinggit cat-fileguard (S1)detect-scope was calling
git diffagainstBASEwithout verifying reachability. Added the same guard already present inpages.yml:Eliminates
fatal: bad objecton force-push, rebase, and first-push scenarios.pages.yml— hard-fail on missing fallback PDFs (M1)When a build is skipped,
docs/reflector.pdfdoesn't exist (it's transient, never committed). The sync and verify steps were unconditionally asserting its presence. Both steps now treat absent fallback PDFs as a warning — Pages serves the last deployed version instead of failing the deployment. PDFs are still required when the build actually ran.release-paper.yml— release creation race condition (M2)Both
publication.ymlandrelease-paper.yml(triggered by tag push) could race to create the same GitHub Release. Added a pre-check that skips creation if the release already exists:Metadata corrections
.zenodo.json—"license": "mit"→"license": "apache-2.0"(correct SPDX identifier)docs/index.html— hardcodedv0.0.1updated tov0.1.1Deliverables
Per issue requirements, three documentation artifacts generated:
audits/publication-infrastructure-audit-followup.md— resolution status for all 12 audit findingsaudits/publication-artifact-inventory.json— artifact lifecycle with producer/consumer/ownership/persistencedocs/publication-workflow-map.md— canonical workflow reference: ownership, trigger conditions, deployment/release/sync flows, scope detection table, coupling points