Remove header "latest ArchivesSpace release" badge in favor of prose on the Getting Started page that auto-updates when a new release is published#305
Merged
Conversation
- Rename getting_started.md -> .mdx to import the new component. - Fix Getting Started page heading hierarchy errors and remove duplicate content.
This new design is based on a personal access token used to dispatch a release event with a data payload from core to the Tech Docs. A new Tech Docs workflow then writes the release data to file, commits, and opens a PR for human review.
brianzelip
force-pushed
the
refactor-the-latest-release-info
branch
from
March 30, 2026 16:44
b5d3750 to
98cfbe5
Compare
Deploying archivesspace-tech-docs with
|
| Latest commit: |
98cfbe5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6fb29bdf.archivesspace-tech-docs.pages.dev |
| Branch Preview URL: | https://refactor-the-latest-release.archivesspace-tech-docs.pages.dev |
thimios
approved these changes
Mar 30, 2026
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.
This PR removes the header “latest ArchivesSpace release” badge and replaces that UX with explicit prose on the Getting Started page.
It also introduces a new automation path so tech-docs can be updated when ArchivesSpace core publishes a release:
System behavior
new-archivesspace-releaseevent to Tech Docs with:tag_namehtml_urlChanges made outside this repo
Next steps
new-archivesspace-releaseevent, see https://github.com/archivesspace/tech-docs/actions/runs/23760785479[0] initiate a dry-run via the GitHub cli:
gh workflow run ".github/workflows/new-archivesspace-release.yml" \ --ref tweak-new-archivesspace-release-workflow \ -f tag_name=v4.2.0 \ -f html_url=https://github.com/archivesspace/archivesspace/releases/tag/v4.2.0References
repository_dispatchevent