Document the September 2026 release

[coryodaniel]

Brings the docs in line with the September 2026 changelog.

Facts were verified against the platform source rather than the blog post, and several details differ from it:

• The atom vocabulary for naming conventions includes {{component.id}}, which the post's table omits.
• The uniqueness rule accepts {{component.id}} plus an environment atom, not only the three-part {{project.id}} form.
• Liquid filters are allowed. Only Liquid tags ({% %}) are rejected. The post says atoms only.
• Connection version ranges are derived from each end's deployed bundle version, not typed by hand. A 0.x bundle buckets at the minor version, so it leaves its range on a minor bump.
• defaultBundleAccess: ALL_PROJECTS creates an ordinary repo:pull grant row that is listed on the repository and revocable with deleteGrant. It applies at repository creation only, and skips resource type repositories.

New pages

• concepts/07-organization-settings.md — naming conventions (atoms, filters, the five validation rules, when the name is applied) and defaultBundleAccess.
• bundle-development/connections-artifacts/02-version-resolution.md — dependencies / resources, the accepted range forms including +dev, and the order a slot is filled in at deploy time (remote reference, then blueprint connection, then environment default).

Changed pages

• concepts/05-connections.md — version ranges on a connection, how they are derived, and why one field can carry several connections.
• concepts/02-artifacts-and-definitions.md — resource types as versioned OCI artifacts; the stale $ref examples replaced.
• concepts/10-deployments.md — separation of duty on approvals.
• bundle-development/connections-artifacts/01-artifact-definition-spec.md — version, environmentDefaultGroup, publishing and immutability, and the deprecated raw JSON schema path. Replaces mass definition publish, which no longer exists.
• bundle-development/connections-artifacts/00-overview.md — described artifacts: as the current key.
• platform-operations/security/03-graphql-permissions.md — createAccessToken was removed from V2.
• getting_started/02-connecting-bundles.md, guides/custom_artifact_definition.md — retired mass definition commands.
• bundle-development/publishing/01-bundle-templates.md — a comment claiming artifacts: is still the current key.
• reference/integrations/01-aws-cost-and-usage-reports.md — Parquet reports.
• platform-operations/self-hosted/01-install.md — MD_DOCS_URL.

Diagrams

Three animated SVGs as MDX components under src/components/Diagrams/, registered globally so pages use them without imports.

They are drawn with Docusaurus CSS variables rather than fixed colors, so they follow the site's light and dark palettes instead of being pinned to one theme. An <img>-referenced SVG cannot see the page's theme, which is why these are inline components. Each holds still under prefers-reduced-motion and carries an aria-label describing what the animation shows.

Verified with a full yarn build: no errors, and onBrokenLinks defaults to throw, so the new cross-links resolve.

Follow-up

#224 tracks converting the remaining bundle examples from connections:/artifacts: to dependencies:/resources:. Each one needs a resource type version chosen against the catalog, so it is not a key rename.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 5, 2026 12:04am UTC

[coryodaniel]

@claude please review

[coryodaniel]

@ChristensenJoe @chrisghill @luismassdriver — could you sweep these for technical accuracy? Preview build is up.

Base: https://docs-git-docs-sept-2026-changelog.preview.massdriver.cloud

New pages

• Organization Settings
• Version Resolution

Changed pages

Connections — has an animated diagram

• Version ranges on a connection
• How the ranges are set
• More than one connection on the same field
• Seeing what an instance is bound to

Deployments — has an animated diagram

• Separation of duty

Resources & Resource Types

• Resource types are versioned
• Usage in massdriver.yaml

Resource Type Spec

• Publishing
• Versions and release channels
• Publishing a raw JSON schema is deprecated
• Referencing in Bundles

Connections & Resources overview — rewritten

• https://docs-git-docs-sept-2026-changelog.preview.massdriver.cloud/bundle-development/connections-artifacts/overview

Smaller edits

• CUR — Parquet reports
• Self-hosted — MD_DOCS_URL
• GraphQL permissions — token mutations
• Bundle templates — legacy key comment
• Getting started — mass resource-type publish
• Custom resource type guide — retired commands

Worth a closer look

These are the points where I wrote something different from the changelog post, after reading the platform source. They are the most likely places for me to be wrong:

• The naming convention atom table includes {{component.id}}, which the post omits.
• The uniqueness rule accepts {{component.id}} plus an environment atom, not only the three-part {{project.id}} form.
• Liquid filters are allowed; only {% %} tags are rejected. The post says atoms only.
• Connection version ranges are derived from each end's deployed bundle version rather than typed by hand, and a 0.x bundle buckets at the minor version.
• defaultBundleAccess: ALL_PROJECTS creates an ordinary repo:pull grant row, applies at repository creation only, and skips resource type repositories.

The three diagrams are inline SVG driven by Docusaurus CSS variables, so please check them in both light and dark mode.