Repository navigation
Conversation
Use a grid layout for better responsiveness and visual appearance. Update styles for improved icon presentation and hover effects.
The footer now contains social media links and a copyright notice. `.clj-kondo` is added to gitignore to prevent it from being committed.
released-version? only matched ^v\d+$, so release tags such as 9.0.0 were filtered out of the build and the version dropdown. Accept legacy v7/v8 branches plus N.N.N tags from major 9 up; v9+ and older 8.x.x tags stay hidden. Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Travis is gone, so merges to staging/master no longer deployed. Build the uberjar, scp it to api-bible-docs and worker, restart the supervisor program, as .travis.yml did. Needs repo secret DEPLOY_SSH_KEY. Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
The Travis-era keys no longer match, so strict host checking refused the connection. Keys taken from the live hosts and cross-checked against the fingerprints already trusted in a maintainer's known_hosts. Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6d40ef90f0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "Legacy v7/v8 branches, plus release tags 9.x.x and up (never v9+). | ||
| Older 8.x.x tags exist in the content repos and must stay hidden." | ||
| [version-key] | ||
| (boolean (re-matches #"^(?:v[78]|(?:9|[1-9]\d+)\.\d+\.\d+)$" version-key))) |
There was a problem hiding this comment.
When a content repository contains a remote branch such as origin/9.0.0, this predicate treats it as a released version even if no 9.0.0 tag exists. reference.git/remote-branches combines branch and tag refs and strips both origin/ and tags/ before version-branches-with-hashes calls this name-only predicate, so the generator can build and publish unreleased branch content in the production version list. Preserve the ref type and apply the new semantic-version rule only to tags.
Useful? React with 👍 / 👎.
| ``` | ||
|
|
||
| Configuration required: | ||
| ```clojure |
There was a problem hiding this comment.
When this Discord namespace is required, the raw Markdown fence and configuration prose are read as Clojure forms, with the final backticks leaving an incomplete reader expression, so namespace loading fails before any notification function can run. This currently remains hidden because the notifier does not require the namespace, but it makes the newly added Discord implementation unusable when wired in.
Useful? React with 👍 / 👎.
2 participants
Merge with a merge commit (
gh pr merge --merge). Do NOT squash or rebase.Squashing diverges the two long-lived branches and the next promotion re-shows the whole history.
Merging this deploys PRODUCTION immediately.
The new GitHub Actions workflow (
.github/workflows/deploy.yml) runs on every push tomaster: builds the jar, copies it to/apps/reference-prod/on api-bible-docs (104.236.66.244) and worker (68.183.148.118), restartsreference-prodon both. Prod currently runs a Feb 2019 jar (matches today'smasterHEAD59fa293), so this ships everything below, not just the dropdown fix.What changes on prod (17 commits)
released-version?acceptsv7/v8+N.N.Ntags from major 9 up;v9, other branches and old8.x.xtags stay hidden (+ unit test). Checked against the real content-repo refs: old filter keptv7 v8 v9, new keeps9.0.0 v7 v8._footer.scss,main_page.clj,common.clj).discord.cljadded,notifier.cljis no-op stubs; config spec no longer requires notification sections. Prod's existing[notifications.*]TOML sections still validate.commons-lang3 3.8.1.scheme.sqluntouched).stagingcode has run on stg since Mar 2025; the stg jars were redeployed from this code today.Heads-up
v9from the prod version list (the build deletes versions that are no longer actual).9.0.0only appears once the content repo has it as a tag (see below).master+9.x.xtags and removal of the same-named9.0.0/v9branches are still pending.adoc/core.clj:196still hardcodes"v8"for tern/json/dts setup.Prep done
*.prod-bak-20261009-1738masterhas no commitsstaginglacks; merge is conflict-freeRollback (per host)
Test plan
supervisorctl status reference-prodRUNNING on both hosts; api.anychart.com returns 200 and the version list is correctJIRA: INFRA-511
🤖 Generated with Claude Code