Repository navigation
Conversation
9 of 17 tasks
bastelfreak
reviewed
Oct 5, 2026
| @@ -1 +1 @@ | |||
| _openfact_5x No newline at end of file | |||
Contributor
There was a problem hiding this comment.
Would it be possible to have \n at the end of the line?
Contributor
Author
There was a problem hiding this comment.
That path is a symlink (mode 120000), so git stores the target name as the blob with no trailing newline; GitHub shows the "No newline" marker on every symlink diff. Adding one would make the link point at "_openfact_6x\n", which doesn't exist. The pre-existing _latest symlinks on master look the same.
miharp
force-pushed
the
docs/promote-9x-latest
branch
from
October 8, 2026 11:48
ff51c16 to
43eb4be
Compare
OpenVox 9.0.0 shipped on 2026-10-02 together with openvox-server and openvoxdb 9.0.0, and openvox-agent 9 bundles OpenFact 6. Point each product's `latest` alias at the new major: the `_<product>_latest` symlinks, the `_latest` nav defaults in _config.yml, the nav_map entries (the frozen 8.x and 5.x entries now own their own URL base), and `latest:` in products.yml. The ecosystem and OpenBolt collections are unchanged. The outdated banner now says the older major is "no longer the current release" rather than "no longer actively updated", since 8.x keeps receiving security releases for a while (OpenVoxProject#503 tracks the lifecycle page). For the same reason the 8.x series refs stay in place instead of being frozen at a final tag; MAINTAINING.md and the products.yml header now say to freeze only once the last maintenance release has shipped. Drift check: every 8.x change since the 9.x copy points is already in 9.x or is deliberately 8.x-only (8.29.0 release notes). No page present in 8.x or 5.x is missing from the new collections, so no /latest/ URL 404s after the switch. Part of OpenVoxProject#456 Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Michael Harp <mike@mikeharp.com>
miharp
force-pushed
the
docs/promote-9x-latest
branch
from
October 8, 2026 15:49
43eb4be to
e330150
Compare
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.
Phase 2 of the major-version cutover in
MAINTAINING.md:/openvox/latest/,/openvox-server/latest/,/openvoxdb/latest/, and/openfact/latest/now serve the 9.x and 6.x collections. bastelfreak confirmed in Slack today that 9.x should be latest. The ecosystem and OpenBolt collections are unchanged.Part of #456.
Changes
_<product>_latestsymlinks._config.yml: the_latestcollections take the 9.x and 6.x navs._data/nav_map.yml: the 9.x and 6.x entries own/latest/; the 8.x and 5.x entries point at their own URL base._data/products.yml:latest:moves to9xand6xfor the four products. The 8.x and 5.xref:series stay as they are rather than being frozen at a final tag, because 8.x is still getting security releases and its generated reference pages should keep tracking them. The products.yml header and MAINTAINING.md step 4 now say to freeze once the last maintenance release has shipped._includes/version-banner.html: the banner on 8.x and 5.x pages now reads "no longer the current release" instead of "no longer actively updated". Add a release lifecycle page (which series are current, maintenance, EOL) #503 tracks the lifecycle page that will say how long 8.x is maintained.Checks
/latest/bookmark 404s. The OpenFactcliandcore_factspages are generated at build time; prod already serves them under/openfact/6.x/.rake test:products_datapasses. Localjekyll buildverified: the/latest/landing pages are OpenVox 9, OpenVox Server 9, OpenVoxDB 9, and OpenFact 6; the banner renders on 8.x and 5.x pages only; the version picker marks 9.x and 6.x as latest; 9.x canonicals point at/latest/and 8.x canonicals at/8.x/.rake test:linkslocally reports only the OpenFactcli.htmlandcore_facts.htmltargets, which are absent untilreferences:allruns in CI.Follow-ups (listed on #456)
openvox8in examples (the VoxBox10.0.0-openvox8.28.1image tag andBEAKER_PUPPET_COLLECTION: openvox8)./latest/links on frozen 8.x pages now land on 9.x docs, as the reference-generation policy intends; authored 8.x pages that link another product's/latest/may want pinning later.Assisted by Claude.