Forge 1.0.0

Forge 1.0.0

Forge 1.0.0 is the first stable release of the RM Industries content-driven
website generator and shared content-model packages.

Highlights

• Generate an accessible Astro article site with Sveltia CMS, RSS, sitemap,
  metadata, responsive navigation, and Catppuccin-based DaisyUI themes.
• Share typed content definitions between Astro collections and Sveltia CMS
  through @rm-industries/content-model.
• Start projects with deterministic materialization, safe destination handling,
  rollback behavior, dependency installation, and optional Git initialization.
• Ship comprehensive formatting, linting, spelling, type, unit, browser,
  accessibility, Lighthouse, dependency, and unused-code checks.
• Include secure GitHub automation for continuous integration, dependency
  updates, analysis, and quality-gated Pages deployment.
• Publish both stable npm packages with verified integrity and SLSA provenance.

Install

npm create @rm-industries/forge

Requirements

• Node.js 22.22.2 or newer in the 22.x line, Node.js 24.x, or Node.js 26.x
• npm 10.9.x or 11.x
• Git unless initialization is disabled with --no-git

Compatibility and migration

No CLI or content-model migration is required from the final 1.0 release
candidates. Stable package versions are:

• @rm-industries/create-forge@1.0.0
• @rm-industries/content-model@1.0.0

Known limitations

• Generated projects are owned source; later Forge versions do not
  automatically migrate existing projects.
• npm is the supported package manager for v1.
• Windows and WSL support is best effort.
• Sveltia remains pre-1.0, so its supported peer range stays bounded to the
  minor version tested by Forge.
• The policy-aware generated-project audit includes time-bounded allowances for
  assessed Lighthouse development-tool advisories.

Evidence and support

The complete 1.0 release evidence
records package integrity, provenance, clean-room generation, 93 cross-browser
tests, and nine Lighthouse runs.

Use GitHub Issues for
reproducible defects and feature proposals. Follow the
security policy to
report vulnerabilities privately.

@rm-industries/create-forge 1.0.0

1.0.0

• Promote the reviewed CLI, deterministic project materialization, and bundled
  default template to the first stable release without command-line contract
  changes from 1.0.0-rc.2; no CLI migration is required.
• Generate an accessible Astro article site with Sveltia CMS, stable
  @rm-industries/content-model@1.0.0, RSS and sitemap output, local fonts,
  DaisyUI themes, comprehensive quality checks, security automation, and a
  gated GitHub Pages deployment.
• Support Node.js 22.22.2/24/26 and npm 10/11. Other package managers and older
  Node.js versions are unsupported; Windows and WSL remain best effort for v1.
• Generated projects are owned source and are not updated automatically by
  later Forge releases. Report reproducible defects and feature proposals
  through Forge GitHub Issues, and report vulnerabilities privately through the
  repository security policy.

@rm-industries/content-model 1.0.0

1.0.0

• Promote the reviewed content-model API and its root, astro, and sveltia
  exports to the first stable release without behavioral or type-level changes
  from 1.0.0-rc.1; no consumer migration is required.
• Support Astro ^7.2.3, Sveltia CMS >=0.203.2 <0.204.0, Node.js
  22.22.2/24/26, and npm 10/11. Astro and Sveltia remain optional peers so
  consumers install only the adapters they use.
• Keep peer ranges intentionally narrow because Sveltia remains pre-1.0 and
  adapter compatibility is expanded only after Forge validation. Generated
  projects are owned source and are not updated automatically by this package.
• Report reproducible defects and feature proposals through Forge GitHub Issues;
  report vulnerabilities privately through the repository security policy.

@rm-industries/create-forge 1.0.0-rc.2

1.0.0-rc.2

• Correct the generated GitHub Pages workflow annotation so its reviewed
  actions/deploy-pages commit is identified as the exact v5.0.0 release.
• Keep action commit pins available for Dependabot updates; workflow-security
  validation, rather than the template verifier, detects stale annotations.
• Existing generated projects have no runtime or CLI migration. They may update
  the annotation from v5 to v5.0.0, or regenerate after reviewing local
  customizations.

@rm-industries/create-forge 1.0.0-rc.1

1.0.0-rc.1

• Bundle the release-candidate @rm-industries/content-model@1.0.0-rc.1
  integration and its tested @sveltia/cms@0.203.2 peer.
• Add nonvisual Forge generator metadata to generated pages so public sites can
  identify their origin without changing visible content.
• Ignore Playwright, Lighthouse, and browser-test output in generated projects.
• Standardize generated Dependabot pull-request labels and expand the generated
  Playwright configuration for explicit browser compatibility runs.
• Freeze and document the supported command-line interface, prompts, defaults,
  validation behavior, exit codes, and Node.js compatibility matrix for 1.0.
• Existing generated projects are not modified automatically. No CLI migration
  is required from 0.4.0-beta.6; projects may adopt the template changes
  individually or regenerate after reviewing local customizations.

v0.6.0 — Documentation complete

Documentation-complete checkpoint

Forge 0.6.0 completes the documentation release gate and validates the complete generated-project experience from the public prerelease.

Included

• Product-level documentation for Forge's packages, architecture, support boundaries, and roadmap.
• Generated-project guides for setup, content and CMS workflows, themes, accessibility, quality troubleshooting, and GitHub Pages deployment.
• Maintainer guidance for synchronization, releases, package publication, and automation.
• Automated documentation validation for links, headings, commands, spelling, and Markdown quality.
• Deployment-aware Playwright and Lighthouse validation for both root sites and GitHub Pages project sites.

Release evidence

• All required work items in #48 are complete.
• @rm-industries/create-forge@0.4.0-beta.6 is publicly available through the npm next tag with provenance.
• A fresh public-package clean-room project completed customization and content authoring from generated documentation.
• Its full npm run quality passed static checks, security policy, 100% unit coverage, production build validation, 31 browser/accessibility checks, and nine Lighthouse runs.

This remains a prerelease roadmap checkpoint. Package consumers should continue using the documented npm prerelease tags until Forge reaches its stable release gate.

@rm-industries/create-forge 0.4.0-beta.6

0.4.0-beta.6

• Run Lighthouse against Astro's production preview server instead of a generic
  static-file server.
• Derive audited URLs from the configured canonical site URL so root and GitHub
  Pages project-path deployments load the same routes and assets as production.
• Add typed URL-generation coverage and document the deployment-aware
  Lighthouse behavior.
• Existing generated projects using a project-path deployment can copy the
  Lighthouse runner, its configuration, and the updated package script without
  regenerating the project.
• Refresh the bundled template lockfile to patched fast-uri 3.1.7 after new
  advisories affected the prior transitive version.

@rm-industries/create-forge 0.4.0-beta.5

0.4.0-beta.5

• Make the generated Playwright configuration wait for the deployed project
  path when a site's canonical URL includes one, such as a GitHub Pages project
  site.
• Resolve browser routes, navigation expectations, internal links, canonical
  metadata, feeds, manifests, and not-found checks against the configured
  deployment base.
• Existing generated projects only need this change when they use a project-path
  deployment. They can copy the updated Playwright configuration, test helper,
  and browser specifications without regenerating the project.

@rm-industries/create-forge 0.4.0-beta.4

0.4.0-beta.4

• Correct the bundled article-authoring example so following it passes the
  generated project's Markdownlint rules without duplicating the document title
  as a top-level heading.
• Add a regression test that keeps the documented article example aligned with
  the article layout's title ownership.
• Existing generated projects need no runtime migration. Projects created with
  beta.3 can remove a repeated top-level heading from articles copied from that
  guide, or copy the corrected guide from this release.

@rm-industries/create-forge 0.4.0-beta.3

0.4.0-beta.3

• Add complete generated-project guides for setup, content and CMS workflows,
  themes, accessibility, quality troubleshooting, and GitHub Pages deployment.
• Refresh the bundled project README and maintainer-facing command guidance so
  public claims correspond to automated checks or explicit manual validation.
• Add repository documentation validation for internal links, heading anchors,
  critical commands, spelling, Markdown quality, and resilient external links.
• Existing generated projects remain unchanged; this release affects projects
  created from the new generator version. Users can copy the new guides without
  regenerating their project, and no runtime migration is required.