Adjust positioning of user email note and permissions heading by joshmgross · Pull Request #2044 · actions/checkout

joshmgross · 2025-01-16T20:42:31Z

The note about the user email should be in the section above this permissions section. Additionally this is all under the "Usage" top-level heading, but "Recommended permissions" isn't directly a usage scenario.

phamhieu1919 · 2025-01-28T17:32:33Z

The note about the user email should be in the section above this permissions section. Additionally this is all under the "Usage" top-level heading, but "Recommended permissions" isn't directly a usage scenario.

…s#2044)

…actions#2044)" This reverts commit 85e6279.

…s#2044)

ghost · 2025-04-09T00:41:13Z

#2044 (comment)

Discussions-To: https://discuss.python.org/t/pep-621-round-3/5472
Status: Final
Type: Standards Track
Topic: Packaging
Created: 22-Jun-2020
Post-History: 22-Jun-2020,
18-Oct-2020,
24-Oct-2020,
31-Oct-2020
Resolution: https://discuss.python.org/t/pep-621-round-3/5472/109

.. canonical-pypa-spec:: :ref:packaging:pyproject-toml-spec

Abstract

This PEP specifies how to write a project's core metadata_ in a
pyproject.toml file for packaging-related tools to consume.

Motivation

The key motivators of this PEP are:

Encourage users to specify core metadata statically for speed,
ease of specification, unambiguity, and deterministic consumption by
build back-ends

Provide a tool-agnostic way of specifying metadata for ease of
learning and transitioning between build back-ends

Allow for more code sharing between build back-ends for the
"boring parts" of a project's metadata

To speak specifically to the motivation for static metadata, that has
been an overall goal of the packaging ecosystem for some time. As
such, making it easy to specify metadata statically is important. This
also means that raising the cost of specifying data as dynamic is
acceptable as users should skew towards wanting to provide static
metadata.

Requiring the distinction between static and dynamic metadata also
helps with disambiguation for when metadata isn't specified. When any
metadata may be dynamic, it means you never know if the absence of
metadata is on purpose or because it is to be provided later. By
requiring that dynamic metadata be specified, it disambiguates the
intent when metadata goes unspecified.

This PEP does not attempt to standardize all possible metadata
required by a build back-end, only the metadata covered by the
core metadata_ specification which are very common across projects
and would stand to benefit from being static and consistently
specified. This means build back-ends are still free and able to
innovate around patterns like how to specify the files to include in a
wheel. There is also an included escape hatch for users and build
back-ends to use when they choose to partially opt-out of this PEP
(compared to opting-out of this PEP entirely, which is also possible).

This PEP is also not trying to change the underlying core metadata_
in any way. Such considerations should be done in a separate PEP which
may lead to changes or additions to what this PEP specifies.

Rationale

The design guidelines the authors of this PEP followed were:

Define a representation of as much of the core metadata_ in
pyproject.toml as is reasonable

Define the metadata statically with an escape hatch for those who
want to define it dynamically later via a build back-end

Use familiar names where it makes sense, but be willing to use more
modern terminology

Try to be ergonomic within a TOML file instead of mirroring how
build back-ends specify metadata at a low-level when it makes sense

Learn from other build back-ends in the packaging ecosystem which
have used TOML for their metadata

Don't try to standardize things which lack a pre-existing standard
at a lower-level

When metadata is specified using this PEP, it is considered
canonical

Specification

When specifying project metadata, tools MUST adhere and honour the
metadata as specified in this PEP. If metadata is improperly specified
then tools MUST raise an error to notify the user about their mistake.

Data specified using this PEP is considered canonical. Tools CANNOT
remove, add or change data that has been statically specified. Only
when a field is marked as dynamic may a tool provide a "new" value.

Details

Table name
''''''''''

Tools MUST specify fields defined by this PEP in a table named
[project]. No tools may add fields to this table which are not
defined by this PEP or subsequent PEPs. For tools wishing to store
their own settings in pyproject.toml, they may use the [tool]
table as defined in :pep:518. The lack of a [project] table
implicitly means the build back-end will dynamically provide all
fields.

name
''''''''

Format: string

Core metadata_: Name
(link <https://packaging.python.org/specifications/core-metadata/#name>__)

Synonyms

Flit_: module/dist-name
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#metadata-section>__)

Poetry_: name
(link <https://python-poetry.org/docs/pyproject/#name>__)

Setuptools_: name
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

The name of the project.

Tools MUST require users to statically define this field.

Tools SHOULD normalize this name, as specified by :pep:503, as soon
as it is read for internal consistency.

version
'''''''''''

Format: string

Core metadata_: Version
(link <https://packaging.python.org/specifications/core-metadata/#version>__)

Synonyms

Flit_: N/A (read from a __version__ attribute)
(link <https://flit.readthedocs.io/en/latest/index.html#usage>__)

Poetry_: version
(link <https://python-poetry.org/docs/pyproject/#version>__)

Setuptools_: version
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

The version of the project as supported by :pep:440.

Users SHOULD prefer to specify already-normalized versions.

description
'''''''''''''''

Format: string

Core metadata_: Summary
(link <https://packaging.python.org/specifications/core-metadata/#summary>__)

Synonyms

Flit_: N/A

Poetry_: description
(link <https://python-poetry.org/docs/pyproject/#description>__)

Setuptools_: description
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

The summary description of the project.

readme
''''''''''

Format: String or table

Core metadata_: Description
(link <https://packaging.python.org/specifications/core-metadata/#description>__)

Synonyms

Flit_: description-file
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#metadata-section>__)

Poetry_: readme
(link <https://python-poetry.org/docs/pyproject/#readme>__)

Setuptools_: long_description
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

The full description of the project (i.e. the README).

The field accepts either a string or a table. If it is a string then
it is the relative path to a text file containing the full
description. Tools MUST assume the file's encoding is UTF-8. If the
file path ends in a case-insensitive .md suffix, then tools MUST
assume the content-type is text/markdown. If the file path ends in
a case-insensitive .rst, then tools MUST assume the content-type
is text/x-rst. If a tool recognizes more extensions than this PEP,
they MAY infer the content-type for the user without specifying this
field as dynamic. For all unrecognized suffixes when a
content-type is not provided, tools MUST raise an error.

The readme field may also take a table. The file key has a
string value representing a relative path to a file containing the
full description. The text key has a string value which is the
full description. These keys are mutually-exclusive, thus tools MUST
raise an error if the metadata specifies both keys.

A table specified in the readme field also has a content-type
field which takes a string specifying the content-type of the full
description. A tool MUST raise an error if the metadata does not
specify this field in the table. If the metadata does not specify the
charset parameter, then it is assumed to be UTF-8. Tools MAY
support other encodings if they choose to. Tools MAY support
alternative content-types which they can transform to a content-type
as supported by the core metadata_. Otherwise tools MUST raise an
error for unsupported content-types.

requires-python
'''''''''''''''''''

Format: string

Core metadata_: Requires-Python
(link <https://packaging.python.org/specifications/core-metadata/#summary>__)

Synonyms

Flit_: requires-python
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#metadata-section>__)

Poetry_: As a python dependency in the
[tool.poetry.dependencies] table
(link <https://python-poetry.org/docs/pyproject/#dependencies-and-dev-dependencies>__)

Setuptools_: python_requires
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

The Python version requirements of the project.

license
'''''''''''

Format: Table

Core metadata_: License
(link <https://packaging.python.org/specifications/core-metadata/#license>__)

Synonyms

Flit_: license
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#metadata-section>__)

Poetry_: license
(link <https://python-poetry.org/docs/pyproject/#license>__)

Setuptools_: license, license_file, license_files
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

The table may have one of two keys. The file key has a string
value that is a relative file path to the file which contains the
license for the project. Tools MUST assume the file's encoding is
UTF-8. The text key has a string value which is the license of the
project whose meaning is that of the License field from the
core metadata_. These keys are mutually exclusive, so a tool MUST
raise an error if the metadata specifies both keys.

A practical string value for the license key has been purposefully
left out to allow for a future PEP to specify support for SPDX_
expressions (the same logic applies to any sort of "type" field
specifying what license the file or text represents).

authors/maintainers
'''''''''''''''''''''''''''

Format: Array of inline tables with string keys and values

Core metadata_: Author/Author-email/Maintainer/Maintainer-email
(link <https://packaging.python.org/specifications/core-metadata/#author>__)

Synonyms

Flit_: author/author-email/maintainer/maintainer-email
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#metadata-section>__)

Poetry_: authors/maintainers
(link <https://python-poetry.org/docs/pyproject/#authors>__)

Setuptools_: author/author_email/maintainer/maintainer_email
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

The people or organizations considered to be the "authors" of the
project. The exact meaning is open to interpretation — it may list the
original or primary authors, current maintainers, or owners of the
package.

The "maintainers" field is similar to "authors" in that its exact
meaning is open to interpretation.

These fields accept an array of tables with 2 keys: name and
email. Both values must be strings. The name value MUST be a
valid email name (i.e. whatever can be put as a name, before an email,
in :rfc:822) and not contain commas. The email value MUST be a
valid email address. Both keys are optional.

Using the data to fill in core metadata_ is as follows:

If only name is provided, the value goes in
Author/Maintainer as appropriate.

If only email is provided, the value goes in
Author-email/Maintainer-email as appropriate.

If both email and name are provided, the value goes in
Author-email/Maintainer-email as appropriate, with the
format {name} <{email}> (with appropriate quoting, e.g. using
email.headerregistry.Address).

Multiple values should be separated by commas.

keywords
''''''''''''

Format: array of strings

Core metadata_: Keywords
(link <https://packaging.python.org/specifications/core-metadata/#keywords>__)

Synonyms

Flit_: keywords
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#metadata-section>__)

Poetry_: keywords
(link <https://python-poetry.org/docs/pyproject/#keywords>_)

Setuptools_: keywords
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

The keywords for the project.

classifiers
'''''''''''''''

Format: array of strings

Core metadata_: Classifier
(link <https://packaging.python.org/specifications/core-metadata/#classifier-multiple-use>__)

Synonyms

Flit_: classifiers
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#metadata-section>__)

Poetry_: classifiers
(link <https://python-poetry.org/docs/pyproject/#classifiers>__)

Setuptools_: classifiers
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

Trove classifiers_ which apply to the project.

urls
''''''''

Format: Table, with keys and values of strings

Core metadata_: Project-URL
(link <https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use>__)

Synonyms

Flit_: [tool.flit.metadata.urls] table
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#metadata-section>__)

Poetry_: [tool.poetry.urls] table
(link <https://python-poetry.org/docs/pyproject/#urls>__)

Setuptools_: project_urls
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

A table of URLs where the key is the URL label and the value is the
URL itself.

Entry points
''''''''''''

Format: Table ([project.scripts], [project.gui-scripts], and
[project.entry-points])

Core metadata: N/A;
Entry points specification

Synonyms

Flit_: [tool.flit.scripts] table for console scripts,
[tool.flit.entrypoints] for the rest
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#scripts-section>__)

Poetry_: [tool.poetry.scripts] table for console scripts
(link <https://python-poetry.org/docs/pyproject/#scripts>__)

Setuptools_: entry_points
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

There are three tables related to entry points. The
[project.scripts] table corresponds to the console_scripts
group in the entry points specification_. The key of the table is the name of the
entry point and the value is the object reference.

The [project.gui-scripts] table corresponds to the gui_scripts
group in the entry points specification_. Its format is the same as
[project.scripts].

The [project.entry-points] table is a collection of tables. Each
sub-table's name is an entry point group. The key and value semantics
are the same as [project.scripts]. Users MUST NOT create
nested sub-tables but instead keep the entry point groups to only one
level deep.

Build back-ends MUST raise an error if the metadata defines a
[project.entry-points.console_scripts] or
[project.entry-points.gui_scripts] table, as they would
be ambiguous in the face of [project.scripts] and
[project.gui-scripts], respectively.

dependencies/optional-dependencies
''''''''''''''''''''''''''''''''''''''''''

Format: Array of :pep:508 strings (dependencies) and a table
with values of arrays of :pep:508 strings
(optional-dependencies)

Core metadata_: Requires-Dist and Provides-Extra
(link <https://packaging.python.org/specifications/core-metadata/#requires-dist-multiple-use>,
link <https://packaging.python.org/specifications/core-metadata/#provides-extra-multiple-use>)

Synonyms

Flit_: requires for required dependencies, requires-extra
for optional dependencies
(link <https://flit.readthedocs.io/en/latest/pyproject_toml.html#metadata-section>__)

Poetry_: [tool.poetry.dependencies] for dependencies (both
required and for development),
[tool.poetry.extras] for optional dependencies
(link <https://python-poetry.org/docs/pyproject/#dependencies-and-dev-dependencies>__)

Setuptools_: install_requires for required dependencies,
extras_require for optional dependencies
(link <https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata>__)

The (optional) dependencies of the project.

For dependencies, it is a key whose value is an array of strings.
Each string represents a dependency of the project and MUST be
formatted as a valid :pep:508 string. Each string maps directly to
a Requires-Dist entry in the core metadata_.

For optional-dependencies, it is a table where each key specifies
an extra and whose value is an array of strings. The strings of the
arrays must be valid :pep:508 strings. The keys MUST be valid values
for the Provides-Extra core metadata_. Each value in the array
thus becomes a corresponding Requires-Dist entry for the matching
Provides-Extra metadata.

dynamic
'''''''''''

Format: Array of strings

Core metadata_: N/A

No synonyms

Specifies which fields listed by this PEP were intentionally
unspecified so another tool can/will provide such metadata
dynamically. This clearly delineates which metadata is purposefully
unspecified and expected to stay unspecified compared to being
provided via tooling later on.

A build back-end MUST honour statically-specified metadata (which
means the metadata did not list the field in dynamic).

A build back-end MUST raise an error if the metadata specifies the
name in dynamic.

If the core metadata_ specification lists a field as "Required",
then the metadata MUST specify the field statically or list it in
dynamic (build back-ends MUST raise an error otherwise, i.e. it
should not be possible for a required field to not be listed somehow
in the [project] table).

If the core metadata_ specification lists a field as "Optional",
the metadata MAY list it in dynamic if the expectation is a
build back-end will provide the data for the field later.

Build back-ends MUST raise an error if the metadata specifies a
field statically as well as being listed in dynamic.

If the metadata does not list a field in dynamic, then a build
back-end CANNOT fill in the requisite metadata on behalf of the user
(i.e. dynamic is the only way to allow a tool to fill in
metadata and the user must opt into the filling in).

Build back-ends MUST raise an error if the metadata specifies a
field in dynamic but the build back-end was unable to provide the
data for it.

Example

::

[project]
name = "spam"
version = "2020.0.0"
description = "Lovely Spam! Wonderful Spam!"
readme = "README.rst"
requires-python = ">=3.8"
license = {file = "LICENSE.txt"}
keywords = ["egg", "bacon", "sausage", "tomatoes", "Lobster Thermidor"]
authors = [
{email = "[email protected]"},
{name = "Tzu-ping Chung"}
]
maintainers = [
{name = "Brett Cannon", email = "[email protected]"}
]
classifiers = [
"Development Status :: 4 - Beta",
"Programming Language :: Python"
]

dependencies = [
"httpx",
"gidgethub[httpx]>4.0.0",
"django>2.1; os_name != 'nt'",
"django>2.0; os_name == 'nt'"
]

[project.optional-dependencies]
test = [
"pytest < 5.0.0",
"pytest-cov[all]"
]

[project.urls]
homepage = "https://example.com"
documentation = "https://readthedocs.org"
repository = "https://github.com"
changelog = "https://github.com/me/spam/blob/master/CHANGELOG.md"

[project.scripts]
spam-cli = "spam:main_cli"

[project.gui-scripts]
spam-gui = "spam:main_gui"

[project.entry-points."spam.magical"]
tomatoes = "spam:main_tomatoes"

Backwards Compatibility

As this prov

Bostt · 2025-04-24T21:35:21Z

gh pr checkout 2044

Bumps actions/checkout from 4 to 5. Release notes Sourced from actions/checkout's releases. v5.0.0 What's Changed Update actions checkout to use node 24 by @salmanmkc in actions/checkout#2226 Prepare v5.0.0 release by @salmanmkc in actions/checkout#2238 ⚠️ Minimum Compatible Runner Version v2.327.1 Release Notes Make sure your runner is updated to this version or newer to use this release. Full Changelog: actions/[email protected] v4.3.0 What's Changed docs: update README.md by @motss in actions/checkout#1971 Add internal repos for checking out multiple repositories by @mouismail in actions/checkout#1977 Documentation update - add recommended permissions to Readme by @benwells in actions/checkout#2043 Adjust positioning of user email note and permissions heading by @joshmgross in actions/checkout#2044 Update README.md by @nebuk89 in actions/checkout#2194 Update CODEOWNERS for actions by @TingluoHuang in actions/checkout#2224 Update package dependencies by @salmanmkc in actions/checkout#2236 Prepare release v4.3.0 by @salmanmkc in actions/checkout#2237 New Contributors @motss made their first contribution in actions/checkout#1971 @mouismail made their first contribution in actions/checkout#1977 @benwells made their first contribution in actions/checkout#2043 @nebuk89 made their first contribution in actions/checkout#2194 @salmanmkc made their first contribution in actions/checkout#2236 Full Changelog: actions/[email protected] v4.2.2 What's Changed url-helper.ts now leverages well-known environment variables by @jww3 in actions/checkout#1941 Expand unit test coverage for isGhes by @jww3 in actions/checkout#1946 Full Changelog: actions/[email protected] v4.2.1 What's Changed Check out other refs/* by commit if provided, fall back to ref by @orhantoy in actions/checkout#1924 New Contributors @Jcambass made their first contribution in actions/checkout#1919 Full Changelog: actions/[email protected] ... (truncated) Changelog Sourced from actions/checkout's changelog. Changelog V5.0.0 Update actions checkout to use node 24 by @salmanmkc in actions/checkout#2226 V4.3.0 docs: update README.md by @motss in actions/checkout#1971 Add internal repos for checking out multiple repositories by @mouismail in actions/checkout#1977 Documentation update - add recommended permissions to Readme by @benwells in actions/checkout#2043 Adjust positioning of user email note and permissions heading by @joshmgross in actions/checkout#2044 Update README.md by @nebuk89 in actions/checkout#2194 Update CODEOWNERS for actions by @TingluoHuang in actions/checkout#2224 Update package dependencies by @salmanmkc in actions/checkout#2236 v4.2.2 url-helper.ts now leverages well-known environment variables by @jww3 in actions/checkout#1941 Expand unit test coverage for isGhes by @jww3 in actions/checkout#1946 v4.2.1 Check out other refs/* by commit if provided, fall back to ref by @orhantoy in actions/checkout#1924 v4.2.0 Add Ref and Commit outputs by @lucacome in actions/checkout#1180 Dependency updates by @dependabot- actions/checkout#1777, actions/checkout#1872 v4.1.7 Bump the minor-npm-dependencies group across 1 directory with 4 updates by @dependabot in actions/checkout#1739 Bump actions/checkout from 3 to 4 by @dependabot in actions/checkout#1697 Check out other refs/* by commit by @orhantoy in actions/checkout#1774 Pin actions/checkout's own workflows to a known, good, stable version. by @jww3 in actions/checkout#1776 v4.1.6 Check platform to set archive extension appropriately by @cory-miller in actions/checkout#1732 v4.1.5 Update NPM dependencies by @cory-miller in actions/checkout#1703 Bump github/codeql-action from 2 to 3 by @dependabot in actions/checkout#1694 Bump actions/setup-node from 1 to 4 by @dependabot in actions/checkout#1696 Bump actions/upload-artifact from 2 to 4 by @dependabot in actions/checkout#1695 README: Suggest user.email to be 41898282+github-actions[bot]@users.noreply.github.com by @cory-miller in actions/checkout#1707 v4.1.4 Disable extensions.worktreeConfig when disabling sparse-checkout by @jww3 in actions/checkout#1692 Add dependabot config by @cory-miller in actions/checkout#1688 Bump the minor-actions-dependencies group with 2 updates by @dependabot in actions/checkout#1693 Bump word-wrap from 1.2.3 to 1.2.5 by @dependabot in actions/checkout#1643 v4.1.3 ... (truncated) Commits 08c6903 Prepare v5.0.0 release (#2238) 9f26565 Update actions checkout to use node 24 (#2226) See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@motss

@salmanmkc

Bumps [actions/checkout](https://github.com/actions/checkout) from 4.2.2 to 5.0.0. Release notes Sourced from actions/checkout's releases. v5.0.0 What's Changed Update actions checkout to use node 24 by @salmanmkc in actions/checkout#2226 Prepare v5.0.0 release by @salmanmkc in actions/checkout#2238 ⚠️ Minimum Compatible Runner Version v2.327.1 Release Notes Make sure your runner is updated to this version or newer to use this release. Full Changelog: actions/[email protected] v4.3.0 What's Changed docs: update README.md by @motss in actions/checkout#1971 Add internal repos for checking out multiple repositories by @mouismail in actions/checkout#1977 Documentation update - add recommended permissions to Readme by @benwells in actions/checkout#2043 Adjust positioning of user email note and permissions heading by @joshmgross in actions/checkout#2044 Update README.md by @nebuk89 in actions/checkout#2194 Update CODEOWNERS for actions by @TingluoHuang in actions/checkout#2224 Update package dependencies by @salmanmkc in actions/checkout#2236 Prepare release v4.3.0 by @salmanmkc in actions/checkout#2237 New Contributors @motss made their first contribution in actions/checkout#1971 @mouismail made their first contribution in actions/checkout#1977 @benwells made their first contribution in actions/checkout#2043 @nebuk89 made their first contribution in actions/checkout#2194 @salmanmkc made their first contribution in actions/checkout#2236 Full Changelog: actions/[email protected] Changelog Sourced from actions/checkout's changelog. Changelog V5.0.0 Update actions checkout to use node 24 by @salmanmkc in actions/checkout#2226 V4.3.0 docs: update README.md by @motss in actions/checkout#1971 Add internal repos for checking out multiple repositories by @mouismail in actions/checkout#1977 Documentation update - add recommended permissions to Readme by @benwells in actions/checkout#2043 Adjust positioning of user email note and permissions heading by @joshmgross in actions/checkout#2044 Update README.md by @nebuk89 in actions/checkout#2194 Update CODEOWNERS for actions by @TingluoHuang in actions/checkout#2224 Update package dependencies by @salmanmkc in actions/checkout#2236 v4.2.2 url-helper.ts now leverages well-known environment variables by @jww3 in actions/checkout#1941 Expand unit test coverage for isGhes by @jww3 in actions/checkout#1946 v4.2.1 Check out other refs/* by commit if provided, fall back to ref by @orhantoy in actions/checkout#1924 v4.2.0 Add Ref and Commit outputs by @lucacome in actions/checkout#1180 Dependency updates by @dependabot- actions/checkout#1777, actions/checkout#1872 v4.1.7 Bump the minor-npm-dependencies group across 1 directory with 4 updates by @dependabot in actions/checkout#1739 Bump actions/checkout from 3 to 4 by @dependabot in actions/checkout#1697 Check out other refs/* by commit by @orhantoy in actions/checkout#1774 Pin actions/checkout's own workflows to a known, good, stable version. by @jww3 in actions/checkout#1776 v4.1.6 Check platform to set archive extension appropriately by @cory-miller in actions/checkout#1732 v4.1.5 Update NPM dependencies by @cory-miller in actions/checkout#1703 Bump github/codeql-action from 2 to 3 by @dependabot in actions/checkout#1694 Bump actions/setup-node from 1 to 4 by @dependabot in actions/checkout#1696 Bump actions/upload-artifact from 2 to 4 by @dependabot in actions/checkout#1695 README: Suggest user.email to be 41898282+github-actions[bot]@users.noreply.github.com by @cory-miller in actions/checkout#1707 v4.1.4 Disable extensions.worktreeConfig when disabling sparse-checkout by @jww3 in actions/checkout#1692 Add dependabot config by @cory-miller in actions/checkout#1688 Bump the minor-actions-dependencies group with 2 updates by @dependabot in actions/checkout#1693 Bump word-wrap from 1.2.3 to 1.2.5 by @dependabot in actions/checkout#1643 v4.1.3 ... (truncated)

@ericsciple

## Release notes Sourced from actions/checkout's releases. v6.0.1 What's Changed Update all references from v5 and v4 to v6 by @ericsciple in actions/checkout#2314 Add worktree support for persist-credentials includeIf by @ericsciple in actions/checkout#2327 Clarify v6 README by @ericsciple in actions/checkout#2328 Full Changelog: actions/checkout@v6...v6.0.1 v6.0.0 What's Changed Update README to include Node.js 24 support details and requirements by @salmanmkc in actions/checkout#2248 Persist creds to a separate file by @ericsciple in actions/checkout#2286 v6-beta by @ericsciple in actions/checkout#2298 update readme/changelog for v6 by @ericsciple in actions/checkout#2311 Full Changelog: actions/checkout@v5.0.0...v6.0.0 v6-beta What's Changed Updated persist-credentials to store the credentials under $RUNNER_TEMP instead of directly in the local git config. This requires a minimum Actions Runner version of v2.329.0 to access the persisted credentials for Docker container action scenarios. v5.0.1 What's Changed Port v6 cleanup to v5 by @ericsciple in actions/checkout#2301 Full Changelog: actions/checkout@v5...v5.0.1 ## Changelog Sourced from actions/checkout's changelog. Changelog v6.0.0 Persist creds to a separate file by @ericsciple in actions/checkout#2286 Update README to include Node.js 24 support details and requirements by @salmanmkc in actions/checkout#2248 v5.0.1 Port v6 cleanup to v5 by @ericsciple in actions/checkout#2301 v5.0.0 Update actions checkout to use node 24 by @salmanmkc in actions/checkout#2226 v4.3.1 Port v6 cleanup to v4 by @ericsciple in actions/checkout#2305 v4.3.0 docs: update README.md by @motss in actions/checkout#1971 Add internal repos for checking out multiple repositories by @mouismail in actions/checkout#1977 Documentation update - add recommended permissions to Readme by @benwells in actions/checkout#2043 Adjust positioning of user email note and permissions heading by @joshmgross in actions/checkout#2044 Update README.md by @nebuk89 in actions/checkout#2194 Update CODEOWNERS for actions by @TingluoHuang in actions/checkout#2224 Update package dependencies by @salmanmkc in actions/checkout#2236 v4.2.2 url-helper.ts now leverages well-known environment variables by @jww3 in actions/checkout#1941 Expand unit test coverage for isGhes by @jww3 in actions/checkout#1946 v4.2.1 Check out other refs/* by commit if provided, fall back to ref by @orhantoy in actions/checkout#1924 v4.2.0 Add Ref and Commit outputs by @lucacome in actions/checkout#1180 Dependency updates by @dependabot- actions/checkout#1777, actions/checkout#1872 v4.1.7 Bump the minor-npm-dependencies group across 1 directory with 4 updates by @dependabot in actions/checkout#1739 Bump actions/checkout from 3 to 4 by @dependabot in actions/checkout#1697 Check out other refs/* by commit by @orhantoy in actions/checkout#1774 Pin actions/checkout's own workflows to a known, good, stable version. by @jww3 in actions/checkout#1776 v4.1.6 Check platform to set archive extension appropriately by @cory-miller in actions/checkout#1732 v4.1.5 Update NPM dependencies by @cory-miller in actions/checkout#1703 Bump github/codeql-action from 2 to 3 by @dependabot in actions/checkout#1694 Bump actions/setup-node from 1 to 4 by @dependabot in actions/checkout#1696 Bump actions/upload-artifact from 2 to 4 by @dependabot in actions/checkout#1695 ... (truncated) ## Commits 8e8c483 Clarify v6 README (#2328) 033fa0d Add worktree support for persist-credentials includeIf (#2327) c2d88d3 Update all references from v5 and v4 to v6 (#2314) 1af3b93 update readme/changelog for v6 (#2311) 71cf226 v6-beta (#2298) 069c695 Persist creds to a separate file (#2286) ff7abcd Update README to include Node.js 24 support details and requirements (#2248) See full diff in compare view ![Dependabot compatibility score](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Issue-ID: CIMAN-33 Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: onap.gh2gerrit <[email protected]> Change-Id: Ia17690fbdd7b5051af7924f7ce869098d1e2a4fa GitHub-PR: #144 GitHub-Hash: cc3d3cb23d3048ef

Adjust positioning of user email note and permissions heading

928458d

joshmgross requested a review from a team as a code owner January 16, 2025 20:42

benwells approved these changes Jan 16, 2025

View reviewed changes

benwells merged commit 85e6279 into main Jan 16, 2025

benwells deleted the joshmgross/README-updates branch January 16, 2025 20:56

peter10012 pushed a commit to xxmime/checkout that referenced this pull request Feb 8, 2025

Adjust positioning of user email note and permissions heading (action…

7713478

…s#2044)

Queenbih87 approved these changes Mar 2, 2025

View reviewed changes

dataway added a commit to dataway/checkout-dw that referenced this pull request Mar 6, 2025

Revert "Adjust positioning of user email note and permissions heading (…

7aeaf66

…actions#2044)" This reverts commit 85e6279.

rostomandjj added a commit to rostomandjj/checkout that referenced this pull request Apr 1, 2025

Adjust positioning of user email note and permissions heading (action…

dba7a82

…s#2044)

ghost reviewed Apr 9, 2025

View reviewed changes

github-actions Bot mentioned this pull request Aug 12, 2025

Bump actions/checkout from 4 to 5 labrynx/auto_comments#27

Merged

tanhongit mentioned this pull request Aug 12, 2025

chore(deps): bump actions/checkout from 4 to 5 cslant/blog-core#62

Merged

4 tasks

SaveTheRbtz mentioned this pull request Aug 12, 2025

build(deps): bump actions/checkout from 4 to 5 SaveTheRbtz/zstd-seekable-format-go#207

Merged

rnelson mentioned this pull request Aug 12, 2025

Bump actions/checkout from 4 to 5 rnelson/RossBot2000#10

Merged

rnelson mentioned this pull request Aug 18, 2025

Bump actions/checkout from 4 to 5 rnelson/aspnetcore-slow-down#28

Closed

ghostflyby mentioned this pull request Aug 18, 2025

Bump actions/checkout from 4 to 5 ghostflyby/mc-mod-skeleton#17

Merged

Boss-1s mentioned this pull request Aug 18, 2025

Bump actions/checkout from 4.2.2 to 5.0.0 Boss-1s/generate-uuid#11

Merged

rnelson mentioned this pull request Aug 18, 2025

Bump actions/checkout from 4 to 5 rnelson/KeysExportViewer#7

Merged

rnelson mentioned this pull request Aug 25, 2025

Bump actions/checkout from 4 to 5 rnelson/Libexec.AspnetCore.EnvironmentHeaders#26

Merged

pgngpp mentioned this pull request Sep 2, 2025

Bump actions/checkout from 4 to 5 pgngpp/skills-github-pgngpp#1

Closed

This was referenced Nov 24, 2025

Bump actions/checkout from 4 to 6 rnelson/aspnetcore-slow-down#30

Merged

Bump actions/checkout from 5 to 6 rnelson/KeysExportViewer#10

Merged

Yossi mentioned this pull request Nov 24, 2025

Bump actions/checkout from 5 to 6 Yossi/outline-tg-bot#54

Merged

rnelson mentioned this pull request Nov 24, 2025

Bump actions/checkout from 5 to 6 rnelson/RossBot2000#12

Merged

TTAPI mentioned this pull request Nov 25, 2025

Bump actions/checkout from 5 to 6 SteamDatabase/BrowserExtension#250

Merged

Chubong630 mentioned this pull request Nov 26, 2025

Bump actions/checkout from 3.6.0 to 6.0.0 Shopify/storefront-api-learning-kit#67

Closed

github-actions Bot mentioned this pull request Nov 26, 2025

Bump actions/checkout from 5 to 6 senzing-garage/sz-sdk-python-core#409

Merged

koodor8888 mentioned this pull request Dec 1, 2025

Bump actions/checkout from 4 to 6 koodor8888/skills-introduction-to-github#3

Open

mamadukes78 mentioned this pull request Dec 1, 2025

Bump actions/checkout from 4 to 6 mamadukes78/AQ-Wedding-Officiant-#3

Open

nik68454 mentioned this pull request Dec 2, 2025

Bump actions/checkout from 4 to 6 nik68454/skills-introduction-to-github#2

Open

LadyO44 mentioned this pull request Dec 11, 2025

Bump actions/checkout from 4 to 6 LadyO44/skills-github-pages#2

Open

lyndseycam mentioned this pull request Jan 2, 2026

Bump actions/checkout from 4 to 6 lyndseycam/skills-introduction-to-github#2

Open

github-actions Bot mentioned this pull request Feb 17, 2026

Bump actions/checkout from 4 to 6 senzing-factory/github-action-make-go-github-file#95

Merged

github-actions Bot mentioned this pull request Apr 9, 2026

Bump actions/checkout from 4 to 6 Senzing/homebrew-senzingsdk#21

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Adjust positioning of user email note and permissions heading#2044

Adjust positioning of user email note and permissions heading#2044
benwells merged 1 commit into
mainfrom
joshmgross/README-updates

joshmgross commented Jan 16, 2025

Uh oh!

phamhieu1919 commented Jan 28, 2025

Uh oh!

ghost Apr 9, 2025

Uh oh!

arturkokurc1-prog May 24, 2026

Uh oh!

Bostt commented Apr 24, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Conversation

joshmgross commented Jan 16, 2025

Uh oh!

phamhieu1919 commented Jan 28, 2025

Uh oh!

ghost Apr 9, 2025

Choose a reason for hiding this comment

Uh oh!

arturkokurc1-prog May 24, 2026

Choose a reason for hiding this comment

Abstract

Motivation

Rationale

Specification

Details

Example

Backwards Compatibility

Uh oh!

Bostt commented Apr 24, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants