fix typo
searching the other codebase seems to confirm this is a typo (results
show "local" not "loca")
https://github.com/search?q=repo%3Agoogleapis%2Frelease-please%20always-link-local&type=code
<!--
Thank you for proposing a pull request! Please note that SOME TESTS WILL
LIKELY FAIL due to how GitHub exposes secrets in Pull Requests from
forks.
Someone from the team will review your Pull Request and respond.
Please describe your change and any implementation details below.
-->
Signed-off-by: Peter W <techieshark@gmail.com>
Co-authored-by: Jeff Ching <chingor@google.com>
Added description how to access monorepo step result outputs using []
syntax
It took me several hours to figure out how to access the outputs of
these monorepo packages. Hopefully, this will save others some time
---------
Signed-off-by: Wolfram Sokollek <8589105+WolfSoko@users.noreply.github.com>
Co-authored-by: Jeff Ching <chingor@google.com>
A very small typo I found in the `README.md` when making sure my usage
of release-please accommodates the new major version.
Changes `relese` to `release`
---------
Signed-off-by: Christian Krogh Nielsen <68676614+banner4422@users.noreply.github.com>
Co-authored-by: Jeff Ching <chingor@google.com>
- Replaced `v3` with `v4` in the examples
- Mapping names to certain references
- Changed `actions/checkout` version from `v2` to `v4`
- Changed `actions/setup-node` version from `v1` to `v4`
Signed-off-by: Rózsa Zoltán <67325669+rozsazoltan@users.noreply.github.com>
Co-authored-by: Jeff Ching <chingor@google.com>
Apparently the only key having the `release_` prefix is the `created`
key, the rest should all be present without that prefix.
I've updated the output keys in the readme, removing the `release_`
prefix.
Signed-off-by: Luca Lanziani <luca.lanziani@gmail.com>
Co-authored-by: Jeff Ching <chingor@google.com>
v3 had this option and must be configurable or at least set to `false`
so that the default behavior is to create a plain `v1.2.3` tag (without
the component name prefixed).
Found this while dogfooding our own usage of the action (in this repo).
Any advanced configuration should be done via a
release-please-config.json.
Fixes#859Fixes#858Fixes#857Fixes#852
feat!: remove most configuration options in favor of manifest
configuration to configure the release-please-action
refactor!: rewrite in typescript
feat!: remove command option in favor of setting `release-type` and
`skip-github-release`/`skip-github-pull-request`
feat!: run on node20
deps!: upgrade release-please to v16
It isn't made explicit that the default token is one that doesn't allow
GitHub Actions CI jobs to run.
Updated the section to make that even more clear.
Signed-off-by: Leland Clemmons <leland.clemmons@gmail.com>
Co-authored-by: Jeff Ching <chingor@google.com>
<!--
Thank you for proposing a pull request! Please note that SOME TESTS WILL
LIKELY FAIL due to how GitHub exposes secrets in Pull Requests from
forks.
Someone from the team will review your Pull Request and respond.
Please describe your change and any implementation details below.
-->
Relating to [release-please
issue](https://github.com/googleapis/release-please/issues/2096)
I was surprised that adding different changelog types result in patch
version bumps. I wasn't expecting this but going through the code it
seemed to be expected but undocumented behavior.
And this is why I would like to document the behavior here so other
people know and can plan whether to use it or not.
cheers!
---------
Signed-off-by: Tommi Tampio <46082658+stutommi@users.noreply.github.com>
Co-authored-by: Jeff Ching <chingor@google.com>
also update the title of the 'adding additional files' to make it a bit
clearer that this section is 'updating additional files' and further
differentiate it from this new section.
* Synchronised action inputs with ReleaserConfig and ManifestOptions from release-please 13.15.0
* fix conflict from merge
* fix merge issue
* fix merge issue
Co-authored-by: Benjamin E. Coe <bencoe@google.com>
Co-authored-by: Jeff Ching <chingor@google.com>
Major update to release-please which consolidates the manifest and single
releaser behavior into a single set of strategies, which can be used
on both split and mono-repos.
feat: adds support for draft pull requests.
feat: adds support for draft releases.
refactor!: if switching to manifest releaser, release_created will only be set if "." path is published.
refactor!: switch to using @actions/core getBooleanInput, accepted values for true = ["true", "True", "TRUE"], accepted values for false = ["false", "False", "FALSE"]
