Category: Upgrade

  • Upgrade and migrate

    In this chapter Upgrade to 0.4.0: Scenario Components migration and behavior review Upgrade OINK: version-to-version steps and breaking changes Migrate from Docsy: move an existing Docsy site to OINK Principles Production sites pin a release tag …

    In this chapter Upgrade to 0.4.0: Scenario Components migration and behavior review Upgrade OINK: version-to-version steps and breaking changes Migrate from Docsy: move an existing Docsy site to OINK Principles Production sites pin a release tag …

  • Migrate an existing Docsy site

    OINK is intended to replace copied common shells, runtimes, and shortcodes without forcing a bulk rewrite of ordinary content. A safe migration removes overrides by dependency, keeps product-specific behavior in the site, and validates a temporary …

    OINK is intended to replace copied common shells, runtimes, and shortcodes without forcing a bulk rewrite of ordinary content. A safe migration removes overrides by dependency, keeps product-specific behavior in the site, and validates a temporary …

  • Upgrade the Oink Hugo Module

    Pin a version Production sites should import a release tag or immutable commit, never an unversioned branch. From the site root, update Oink to a specific ref: BASH hugo mod get github.com/pgsty/oink@TARGET_VERSION hugo mod tidy Replace …

    Pin a version Production sites should import a release tag or immutable commit, never an unversioned branch. From the site root, update Oink to a specific ref: BASH hugo mod get github.com/pgsty/oink@TARGET_VERSION hugo mod tidy Replace …

  • Upgrade to Oink 0.4.0

    Oink 0.4.0 is the consolidated Scenario Components release. Reading & Release, Landing, and Book were originally designed as 0.4, 0.5, and 0.6 tracks but ship together under the single public v0.4.0 tag. Do not pin the historical design numbers. …

    Oink 0.4.0 is the consolidated Scenario Components release. Reading & Release, Landing, and Book were originally designed as 0.4, 0.5, and 0.6 tracks but ship together under the single public v0.4.0 tag. Do not pin the historical design numbers. …