Skip to content

Redirect pages from the migration sheet's Redirect Only tab #4218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
matthewhelmke merged 1 commit into from
Oct 16, 2026
Merged

Redirect pages from the migration sheet's Redirect Only tab #4218

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion config/_default/config.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,6 @@ notAlternative = true
filename = "sitemap.xml"
priority = 0.5
[taxonomies]
contributor = "contributors"
tags = "tags"
[related]
# Only include matches with rank >= threshold
Expand Down
6 changes: 0 additions & 6 deletions config/_default/menus/menus.en.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,12 +137,6 @@
identifier = "menu-security"
weight = 20

[[main]]
name = "What is software supply chain security"
url = "/software-security/what-is-software-supply-chain-security/"
parent = "menu-security"
weight = 20


[[social]]
name = "X"
Expand Down
6 changes: 3 additions & 3 deletions content/chainguard/containers/concepts/lifecycle-and-eol/eol-grace-period/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ linktitle: "EOL grace period"
type: "article"
description: "Understanding Chainguard's end-of-life (EOL) grace period."
date: 2025-05-14T08:49:31+00:00
lastmod: 2026-10-08T13:39:28+00:00
lastmod: 2026-10-15T14:26:56+00:00
draft: false
tags: ["Chainguard Containers"]
images: []
Expand All @@ -21,7 +21,7 @@ aliases:

Typically, specific versions of software receive updates on a schedule for a set amount of time. Eventually, though, every version of software will stop receiving support. When project maintainers stop providing updates, it's known as the *End-of-Life* (EOL) stage.

It's recommended that when a software version reaches the EOL phase, users should migrate their projects to a later version, as [EOL software is known to accumulate vulnerabilities](/chainguard/containers/concepts/lifecycle-and-eol/how-eol-software-accumulates-cves/). However, there are cases where an organization may want to continue using a container image after it has reached end-of-life. This could be because an image reaches EOL before the organization's release schedule, or perhaps later image versions have one or more issues that prevent the organization from upgrading.
It's recommended that when a software version reaches the EOL phase, users should migrate their projects to a later version, as [EOL software is known to accumulate vulnerabilities](https://www.chainguard.dev/unchained/why-end-of-life-software-means-400-cves-per-year). However, there are cases where an organization may want to continue using a container image after it has reached end-of-life. This could be because an image reaches EOL before the organization's release schedule, or perhaps later image versions have one or more issues that prevent the organization from upgrading.

To help in situations like this, Chainguard offers an end-of-life grace period for eligible Containers to all Chainguard Containers customers. This article provides an overview of Chainguard's EOL grace period, and also includes a brief introduction to using Chainguard's API to retrieve information about an image's EOL grace period status.

Expand Down Expand Up @@ -175,4 +175,4 @@ Of course, you won't use `curl` to interact with the Chainguard API in most scen

Chainguard's EOL grace period gives customers the opportunity to continue to receive best-effort CVE remediated updates on EOL images, while they work on transitioning to a newer upstream version.

For more information on the EOL grace period, [please contact us](https://www.chainguard.dev/contact?utm_source=cg-academy&utm_medium=referral&utm_campaign=dev-enablement). Additionally, our doc outlining the [Chainguard Containers product release lifecycle](/chainguard/containers/concepts/lifecycle-and-eol/versions/) can be helpful for understanding Chainguard’s approach to updates, releases, and versions within Chainguard Containers. Finally, our conceptual article on [How end-of-life software accumulates vulnerabilities](/chainguard/containers/concepts/lifecycle-and-eol/how-eol-software-accumulates-cves/) is helpful for understanding the risk involved with using end-of-life software by outlining how EOL images accrue vulnerabilities and where they accumulate.
For more information on the EOL grace period, [please contact us](https://www.chainguard.dev/contact?utm_source=cg-academy&utm_medium=referral&utm_campaign=dev-enablement). Additionally, our doc outlining the [Chainguard Containers product release lifecycle](/chainguard/containers/concepts/lifecycle-and-eol/versions/) can be helpful for understanding Chainguard’s approach to updates, releases, and versions within Chainguard Containers. Finally, our blog post [Why end-of-life software means 400+ CVEs per year](https://www.chainguard.dev/unchained/why-end-of-life-software-means-400-cves-per-year) explains how end-of-life software accumulates vulnerabilities.
Binary file removed ...ntainers/concepts/lifecycle-and-eol/how-eol-software-accumulates-cves/EOL_1.png
View file
Open in desktop
Binary file not shown.
Binary file removed ...ntainers/concepts/lifecycle-and-eol/how-eol-software-accumulates-cves/EOL_3.png
View file
Open in desktop
Binary file not shown.
122 changes: 0 additions & 122 deletions ...ontainers/concepts/lifecycle-and-eol/how-eol-software-accumulates-cves/index.md
View file
Open in desktop

This file was deleted.

4 changes: 2 additions & 2 deletions ...uard/containers/security-and-compliance/updating-containers/dependabot/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ aliases:
type: "article"
description: "How to configure Dependabot to authenticate to your private cgr.dev registry and open pull requests that update Chainguard Containers"
date: 2026-09-03T00:00:00+00:00
lastmod: 2026-09-28T14:00:04+00:00
lastmod: 2026-10-15T14:26:56+00:00
draft: false
tags: ["Chainguard Containers"]
images: []
Expand Down Expand Up @@ -171,5 +171,5 @@ If the job log shows a successful run but no pull requests, check the following:
## Learn more

* [Using Renovate with Chainguard Containers](/chainguard/containers/security-and-compliance/updating-containers/renovate/) covers the equivalent setup for teams outside GitHub, or teams that want short-lived credentials through an assumable identity.
* [Strategies and tooling for updating containers](/chainguard/containers/security-and-compliance/updating-containers/strategies-tools-updating-images/) compares the wider range of update tools.
* [Stay secure: Strategies and tooling for updating container images](https://www.chainguard.dev/unchained/stay-secure-strategies-and-tooling-for-updating-container-images), on the Chainguard blog, compares the wider range of update tools.
* [Authenticating to the Chainguard registry](/chainguard/containers/registry/authenticating/) documents pull tokens and the other authentication options in full.
4 changes: 2 additions & 2 deletions ...uard/containers/security-and-compliance/updating-containers/digestabot/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ aliases:
type: "article"
description: "How to configure Digestabot to keep digest-pinned references to Chainguard Containers current, including authenticating to a private cgr.dev registry"
date: 2024-02-07T15:21:01+00:00
lastmod: 2026-09-28T14:00:04+00:00
lastmod: 2026-10-15T14:26:56+00:00
draft: false
tags: ["Chainguard Containers"]
images: []
Expand Down Expand Up @@ -318,6 +318,6 @@ So please try it out and let me know if you have any questions.

* [Using Dependabot with Chainguard Containers](/chainguard/containers/security-and-compliance/updating-containers/dependabot/) covers the tool to pair with Digestabot for moving between version streams.
* [Using Renovate with Chainguard Containers](/chainguard/containers/security-and-compliance/updating-containers/renovate/) covers the equivalent setup for teams outside GitHub.
* [Strategies and tooling for updating containers](/chainguard/containers/security-and-compliance/updating-containers/strategies-tools-updating-images/) compares the wider range of update tools.
* [Stay secure: Strategies and tooling for updating container images](https://www.chainguard.dev/unchained/stay-secure-strategies-and-tooling-for-updating-container-images), on the Chainguard blog, compares the wider range of update tools.
* [Considerations for keeping containers up to date](/chainguard/containers/security-and-compliance/updating-containers/considerations-for-image-updates/) covers the tradeoffs behind an update policy.
* [Inspecting Chainguard Containers](/chainguard/containers/troubleshooting/inspecting-containers/) explains what a digest is and why pinning to one matters.
4 changes: 2 additions & 2 deletions ...nguard/containers/security-and-compliance/updating-containers/renovate/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ aliases:
type: "article"
description: "How to use Renovate to automatically keep Chainguard Containers, Helm charts and packages updated"
date: 2023-09-05T11:07:52+02:00
lastmod: 2026-10-08T13:25:53+00:00
lastmod: 2026-10-15T14:26:56+00:00
draft: false
tags: ["Chainguard Containers"]
images: []
Expand Down Expand Up @@ -667,7 +667,7 @@ These can be safely ignored. They are caused by Renovate using the `org.opencont

* [Using Digestabot with Chainguard Containers](/chainguard/containers/security-and-compliance/updating-containers/digestabot/) covers Chainguard's own GitHub Action for keeping digest-pinned references current.
* [Using Dependabot with Chainguard Containers](/chainguard/containers/security-and-compliance/updating-containers/dependabot/) covers the equivalent setup for teams already using Dependabot.
* [Strategies and tooling for updating containers](/chainguard/containers/security-and-compliance/updating-containers/strategies-tools-updating-images/) compares the wider range of update tools.
* [Stay secure: Strategies and tooling for updating container images](https://www.chainguard.dev/unchained/stay-secure-strategies-and-tooling-for-updating-container-images), on the Chainguard blog, compares the wider range of update tools.
* [Considerations for keeping containers up to date](/chainguard/containers/security-and-compliance/updating-containers/considerations-for-image-updates/) covers the tradeoffs behind an update policy.
* [Authenticating to the Chainguard registry](/chainguard/containers/registry/authenticating/) documents pull tokens and the other authentication options in full.
* [Renovate's APK datasource documentation](https://docs.renovatebot.com/modules/datasource/apk/) covers every `registryUrl` query parameter Renovate supports.
Loading
Loading