Skip to content

GitHub Container Registry: New landing pages with repository linking

We've refreshed the landing page for containers in GitHub Container Registry. You can now see an organized snapshot of the description, versions, tags, and downloads.

You can also connect your containers to a repository via an OCI label or through the UI. The landing page will show relevant links and content from the linked repository.

Container landing page

The Checks API now has a limit of 1,000 check runs with the same name per check suite.

Using checks, you can run checks against code changes in a repository, as either a check run or a check suite. For two check runs with the same name, only the most recent check run is displayed in the UI, but older versions can be queried via the API.

The new limit restricts how many check runs are stored with the same name, to a maximum of 1,000. If the limit is exceeded, only the most recent 1,000 runs are stored, and older runs are deleted. This change affects both newly created check suites and new check runs in existing check suites. Existing check runs are not affected unless the limit is newly exceeded.

See more

Secret leaks are one of the most common security mistakes, and they can have disastrous consequences. GitHub Secret Scanning looks for leaked secrets in all public repositories, and enrolled private repositories, and works with the issuer to notify the developer and/or revoke the token as appropriate. This protects users from fraud and data leaks.

In addition to our 29 existing partners, GitHub has partnered with Clojars, Mailchimp, Finicity, and Plivo to scan for their developer tokens! This brings our total number of token scanning partners to 33.

See more