Update tj-actions/changed-files action to v44 #113
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v42->v44Release Notes
tj-actions/changed-files (tj-actions/changed-files)
v44Compare Source
Changes in v44.0.0
🔥🔥 BREAKING CHANGE 🔥🔥
Overview
We've made a significant update to how pull requests (PRs) from forked repositories are processed. This improvement not only streamlines the handling of such PRs but also fixes a previously identified issue.
Before the Change
Previously, when you created a pull request from a forked repository, any files changed in the target branch after the PR creation would erroneously appear as part of the PR's changed files. This made it difficult to distinguish between the actual changes introduced by the PR and subsequent changes made directly to the target branch.
What Has Changed
With this update, a pull request from a fork will now only include the files that were explicitly changed in the fork. This ensures that the list of changed files in a PR accurately reflects the contributions from the fork, without being muddled by unrelated changes to the target branch.
Important Note for Users
To take advantage of this new behaviour, it's necessary to specify the fork repository explicitly when performing the checkout step in your workflows. Below is an example configuration that demonstrates how to do this:
This modification ensures that your workflows correctly identify and interact with the source repository for PRs originating from forks.
What's Changed
New Contributors
Full Changelog: tj-actions/changed-files@v43.0.1...v44.0.0
v43Compare Source
Changes in v43.0.1
What's Changed
Full Changelog: tj-actions/changed-files@v43...v43.0.1
Changes in v43.0.0
🔥🔥 BREAKING CHANGE 🔥🔥
any_{changed, modified, deleted}outputs now returntruewhen no file/directory patterns are specified.What's Changed
any_{changed, modified, deleted}outputs when no patterns are specified by @jackton1 in https://github.com/tj-actions/changed-files/pull/1988Full Changelog: tj-actions/changed-files@v42...v43.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.