Repository navigation
Promote main to staging - #784
Merged
Merged
Conversation
Promotion is now a merge into the environment branch instead of a manual dispatch: main deploys friends, staging deploys staging, production deploys production, each after Build Test Lint passes on a push. Dispatch stays for ad-hoc and rollback deploys and gains friends as an option. notch8/actions v1.0.12 is required: earlier tags deploy the default branch's image and ops templates under a workflow_run trigger. Assisted by: Opus 5
Deploy now triggers off a successful Build Test Lint push run, so the environment branches need it to run, and promotion PRs into them need the same checks main gets. Assisted by: Opus 5
Copied from samvera/hyku. The labels feed release-drafter's categories and version bump, so a PR without one would be silently misfiled in the notes. Assisted by: Opus 5
Adapted from samvera/hyku#3323. A staging push drafts v<next>-rc as a prerelease, a production push drafts v<next>. Tags continue this repo's v0.2.x line, not Hyku's version. Drafts only: Hyku's version-file bump and bot push are dropped, since the knapsack version tracks the pinned Hyku and the environment branches are protected. A human publishes the draft. Categories match .github/release.yml so drafted and generated notes agree. Ref: - samvera/hyku#3323 Assisted by: Opus 5
Copied from samvera/hyku#3333. A hotfix merged straight into staging or production gets a draft PR back down (staging -> main, production -> staging) so the branches do not drift. The notch8 GitHub App behind AUTO_MERGER_APP_ID / AUTO_MERGER_APP_PRIVATE_KEY does not exist yet, so the job skips with a notice until the secrets are set rather than failing every push. Ref: - samvera/hyku#3333 Assisted by: Opus 5
Matches notch8/hykuup_knapsack's config, minus the reviewers key GitHub deprecated for Dependabot. A CODEOWNERS entry on /hyrax-webapp requests the review instead. Assisted by: Opus 5
HykuKnapsack::VERSION had stayed at 7.0.0 while hyrax-webapp moved to Hyku 7.1.0. It is meant to name the Hyku it runs, so it now fails CI when the two differ, with the version to set. Release tags stay on the v0.2.x line. Assisted by: Opus 5
CLAUDE.md is gitignored in this repo, so the repo-specific deploy facts go in the README, which both people and agents read. The production window is not settled yet. Assisted by: Opus 5
Assisted by: Opus 5
Rulesets require it by job name, so one name works in all three repos. Assisted by: Opus 5
Friday cutoff, Monday promotion and notice, client review of needs-client-review tickets through Wednesday, Thursday release. Assisted by: Opus 5
Matches hykuup: two quick pushes cannot race on the same merge-down PR, and a queued draft run on one branch is not dropped by another branch. Assisted by: Opus 5
Hyku dropped database-changes in samvera/hyku#3323; database work carries the usual severity labels. Dependabot bumps now get their own Dependencies section. Assisted by: Opus 5
PR has required labels is a required check, so an unlabelled merge-down PR sat red until someone added a label by hand. Merge-downs carry changes already in a release, so they stay out of the notes. Assisted by: Opus 5.5
The merge-down script was a copy of Hyku's, repeated in every knapsack. It now lives once in notch8/actions (notch8/actions#123). Assisted by: Opus 5
One copy in notch8/actions instead of one per knapsack. Drafts now note the pinned Hyku version and SHA in the footer. Assisted by: Opus 5
The shared check pins the label-checker image by digest instead of running :latest with the repo token. The required check is now named `check_pr_labels / PR has required labels`. Assisted by: Opus 5
The knapsack keeps its own version; release tags already carry the repo's own line. Release drafts record the pinned Hyku version and SHA. Assisted by: Opus 5
The team is managed in notch8-ops, so onboarding and offboarding happen in one place for every knapsack. Assisted by: Opus 5
Keeps tag and SHA pins current without hand edits. Assisted by: Opus 5
The friends environment isn't functional. dev matches hykuup and utk. The template drops the pittir-staging.hykucommons.org Cloudflare test host so a client domain doesn't follow it onto dev. Assisted by: Opus 5
The github.com blob ?raw=true redirect intermittently returns 503, which fails every image build at this ADD. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replaces the hand-run `gh release edit --target <sha>` step with notch8/actions' publish-release, which waits for approval on the production environment and pins the draft to the deployed commit. Assisted by: Opus 5
Assisted by: Opus 5
Brings DateRangeIndexing, which writes integer years from date_created to date_range_isim at index time, and the blacklight_range_limit and codemirror-autorefresh loading fixes that clear the "See almond README: incorrect module build" error on every page. It also brings samvera/hyku#3301, the one other change between the pins: the PDF.js viewer no longer scrolls the page to its iframe on load, and its search param is URL-encoded and skipped when blank. Stops short of Hyku main on purpose: samvera/hyku#3288, merged right after, switches the Solr schema from Trie to Point field types, and any collection whose configset is replaced while holding documents returns wrong results or 500s until fully reindexed (samvera/hyku#3355). That migration gets its own ticket. The knapsack version follows Hyku's 7.1.0. Ref: - samvera/hyku#3313 - samvera/hyku#3301 - samvera/hyku#3355 Assisted by: Opus 5.5
The facet ranged over date_ssi, a string field, so Solr's stats sorted values lexically: "1895-1905" came first and "ca. 1967" sorted after every digit-leading value, including "2026". Hanover's facet reported "1895-1905 to ca. 1967" while holding 2026 works, and showed the raw strings as its bounds. date_range_isim holds integers, so its min and max are real years. The label stays "Date Created" so patrons see no rename, and comes from blacklight.search.fields.facet.date_range_isim in each pals locale, reusing the existing date_created_tesim translation. With Hyku's JS loading fixed, the histogram and slider pals turned off in de326b4 come back on, matching stock Hyku. The fixed assumed_boundaries of 1100 to now+2 go too: they squeezed Hanover's chart into its right fifth. Hyku's own 1800 floor would cut off Hanover's 544 pre-1800 years (back to 1488), so the bounds now come from each tenant's results, at the cost of the gem's one extra request. The remaining options were gem defaults (num_segments: 10) or ignored (browsers drop maxlength on number inputs), so the facet takes the gem's defaults with range: true. Existing works only get date_range_isim when reindexed. Ref: - #758 Assisted by: Opus 5.5
Hyku only spans "/" intervals and reads a year at the very start of a
value. Of Hanover's 3,864 works, 966 use "1890-1910", which would index
as 1890 alone; about 200 use "1860, 1861, 1862" lists, which would index
as the first year; and "ca. 1967" would index as nothing. With this,
3,689 works land on their years and 3 stay unparsed ("Early 1920's",
"0", "Unknown"), next to 172 with no date.
The range accepts a hyphen, en dash or em dash, since catalog data that
has passed through Word or a spreadsheet often carries "1890–1910". It
requires four digits on both sides so ISO "2020-05" and "2020-05-15"
still read as 2020. Worth taking upstream to Hyku, after
which this decorator can go.
Ref:
- #758
Co-authored-by: LaRita Robinson <laritakr@users.noreply.github.com>
Assisted by: Opus 5.5
The range facet's missing row is labeled by Blacklight's blacklight.search.facets.missing, whose default is "[Missing]". Hyku translates it in samvera/hyku#3325, which merged after the pinned commit; these are the same values, and become redundant on the next Hyku bump. Ref: - samvera/hyku#3325 Assisted by: Opus 5.5
🐛 Range Date Created over indexed years
The template renamed from friends pointed dev at the old Postgres and the shared besties-fcrepo-clone bucket. #761 has the settings the running palni-palci-knapsack-dev uses (zalando pooler, its own fcrepo bucket, schema_migrations pre-setup), so main's first auto-deploy to dev keeps them. Assisted by: Opus 5
🚀 Adopt Hyku's release and auto-deploy process
Bumps [notch8/actions/.github/workflows/test.yaml](https://github.com/notch8/actions) from 1.0.10 to 1.0.11. - [Release notes](https://github.com/notch8/actions/releases) - [Commits](notch8/actions@v1.0.10...v1.0.11) --- updated-dependencies: - dependency-name: notch8/actions/.github/workflows/test.yaml dependency-version: 1.0.11 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [notch8/actions/.github/workflows/report.yaml](https://github.com/notch8/actions) from 1.0.10 to 1.0.11. - [Release notes](https://github.com/notch8/actions/releases) - [Commits](notch8/actions@v1.0.10...v1.0.11) --- updated-dependencies: - dependency-name: notch8/actions/.github/workflows/report.yaml dependency-version: 1.0.11 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [notch8/actions/.github/workflows/build.yaml](https://github.com/notch8/actions) from 1.0.10 to 1.0.11. - [Release notes](https://github.com/notch8/actions/releases) - [Commits](notch8/actions@v1.0.10...v1.0.11) --- updated-dependencies: - dependency-name: notch8/actions/.github/workflows/build.yaml dependency-version: 1.0.11 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [notch8/actions/.github/workflows/lint.yaml](https://github.com/notch8/actions) from 1.0.10 to 1.0.11. - [Release notes](https://github.com/notch8/actions/releases) - [Commits](notch8/actions@v1.0.10...v1.0.11) --- updated-dependencies: - dependency-name: notch8/actions/.github/workflows/lint.yaml dependency-version: 1.0.11 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…actions/dot-github/workflows/report.yaml-1.0.11 Bump notch8/actions/.github/workflows/report.yaml from 1.0.10 to 1.0.11
…actions/dot-github/workflows/lint.yaml-1.0.11 Bump notch8/actions/.github/workflows/lint.yaml from 1.0.10 to 1.0.11
…actions/dot-github/workflows/build.yaml-1.0.11 Bump notch8/actions/.github/workflows/build.yaml from 1.0.10 to 1.0.11
…actions/dot-github/workflows/test.yaml-1.0.11 Bump notch8/actions/.github/workflows/test.yaml from 1.0.10 to 1.0.11
A metadata profile property with the mesh controlled-values source 500s the new and edit work forms with "Qa::Authorities::Mesh#all is unimplemented" (found on HykuUp's St. Jude tenant). Since samvera/hyku#3225, which pals' Hyku pin includes, the form helper takes any registered local subauthority for a select, mesh included, and asks it for every term; Mesh only searches, and the NotImplementedError it raises slips past the helper's rescue StandardError. Rescuing it lets the helper fall through to the mesh autocomplete Hyku already configures. Same fix as samvera/hyku#3371 and hykuup_knapsack#806; this goes once the pin includes it. Assisted by: Claude Opus 5.5
`staging` -> `main`: merge down the flexible form hotfix
Bumps [hyrax-webapp](https://github.com/samvera/hyku) from `c3f1255` to `198f495`. - [Release notes](https://github.com/samvera/hyku/releases) - [Commits](samvera/hyku@c3f1255...198f495) --- updated-dependencies: - dependency-name: hyrax-webapp dependency-version: 198f49506b020af8143bca36e3f86309a9597143 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A notch8/actions release opened one PR per workflow file it bumps (five on 2026-10-05). Grouping makes it one PR per week. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Were having trouble deploying to r2-friends because they couldn't schedule at current requests, which was higher than needed
🔧 Group Dependabot's actions bumps into one PR
📚 Add the client announcement channel and approval gate to Deploying
…p-198f495 Bump hyrax-webapp from `c3f1255` to `198f495`
Reduce CPU requests on dev and staging deploys
🐛 Offer MeSH as autocomplete instead of 500ing the form
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
If your organization's extra usage balance is empty, an organization admin can add extra usage credits at claude.ai/admin-settings/usage. If its monthly spend limit was reached, an admin can raise it on the same page. If neither applies, contact Anthropic support.
Once extra usage is available, someone with write access to this repository can comment @claude review on this pull request to trigger a review.
ShanaLMoore
approved these changes
Oct 6, 2026
ShanaLMoore
enabled auto-merge
October 6, 2026 21:22
This branch was successfully deployed
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
3 participants
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.
Promotion from main.
Ships to staging: the MeSH autocomplete fix so the form no longer 500s (#773), the Date Created range facet (#760, with the Hyku bump to 198f495 via #776), the release-process workflows (#752), Actions bumps (#765-768, #778), README cadence/announcement notes (#777), and reduced dev/staging CPU requests (#779).
Note: staging is currently running
3b64e2a8, dispatched from theright_size_friends_requestsbranch before #779 merged. This promotion brings thestagingbranch back in line with what is running plus the rest ofmain.🤖 Generated with Claude Code