Skip to content

fix: publish canonical draft filename #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nkavian merged 1 commit into from
Sep 16, 2026
Merged

fix: publish canonical draft filename #53

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/deploy-pages.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ jobs:
mkdir release-artifacts
for extension in html pdf txt xml; do
cp "${draft}.${extension}" release-artifacts/
cp "${draft}.${extension}" "release-artifacts/offering-discovery-protocol.${extension}"
cp "${draft}.${extension}" "release-artifacts/draft-kavian-offering-discovery-protocol.${extension}"
done

- name: Publish latest release artifacts
Expand Down
5 changes: 5 additions & 0 deletions ietf/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,11 @@ under ignored `artifacts/` and regenerate every committed site artifact under `d
ietf idnits` to render the draft and inspect its text artifact with idnits. The full check also
rejects hard-coded section numbers into external Internet-Drafts and a stale site index.

The deployment workflow publishes the draft under its immutable versioned filename and a stable
filename without the revision suffix. Public website links use the stable
`draft-kavian-offering-discovery-protocol.*` filenames so advancing the draft does not require
changing those links.

Rendering derives RFC bibliography dependencies from draft frontmatter and seeds the ignored local
cache from the official `ietf-tools/bibxml-data-archive` before invoking kramdown-rfc. The source
draft remains the reference manifest; no separate RFC list is maintained.
Expand Down
4 changes: 4 additions & 0 deletions ietf/guides/internet-draft-revision-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,6 +134,10 @@ The deployment workflow separately moves the replaceable `latest` Git tag and Gi
deployed `main` commit. `latest` is a convenience snapshot; it does not replace the immutable tag
and release for a submitted revision.

The `latest` release publishes the draft under both its immutable versioned filename and the stable
`draft-kavian-offering-discovery-protocol.*` filenames without the revision suffix. Public website
links use the stable filenames so advancing a revision does not require changing those links.

Final verification requires all of the following:

- Datatracker shows the intended revision.
Expand Down