Skip to content
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.

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

chore(deps): bump tj-actions/changed-files from 43.0.1 to 44.0.0 #7817

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 1, 2024

Bumps tj-actions/changed-files from 43.0.1 to 44.0.0.

Release notes

Sourced from tj-actions/changed-files's releases.

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.


What's Changed

New Contributors

Full Changelog: tj-actions/changed-files@v43.0.1...v44.0.0

Changelog

Sourced from tj-actions/changed-files's changelog.

Changelog

44.0.0 - (2024-03-27)

🐛 Bug Fixes

  • Ensure the fork remote doesn't exists before creating it (#2012) (4bbd49b) - (Tonye Jack)
  • Update previos sha for forks (#2011) (f0e7702) - (Tonye Jack)
  • Update to add the fork remote (#2010) (6354e6c) - (Tonye Jack)
  • Check for setting remote urls for forks (#2009) (1176164) - (Tonye Jack)
  • Bug with prs from forks returning incorrect set of changed files (#2007) (4ff7936) - (Tonye Jack)

➖ Remove

🔄 Update

  • Updated README.md (#2016)

Co-authored-by: jackton1 17484350+jackton1@users.noreply.github.com (2d756ea) - (tj-actions[bot])

  • Update README.md (2d21bbb) - (Tonye Jack)
  • Updated README.md (#2013)

Co-authored-by: jackton1 17484350+jackton1@users.noreply.github.com (2ca8dc4) - (tj-actions[bot])

  • Update README.md (4621617) - (tonyejack1)
  • Update README.md (c6557ed) - (Tonye Jack)
  • Update README.md (0713a11) - (Tonye Jack)

⚙️ Miscellaneous Tasks

  • Update description of outputs removing asterisks (#2015) (ce497c3) - (tonyejack1)
  • Update description of other_deleted_files output (#2008) (ee096d6) - (tonyejack1)
  • deps: Update typescript-eslint monorepo to v7.4.0 (0647424) - (renovate[bot])
  • deps: Lock file maintenance (efe5e6c) - (renovate[bot])

⬆️ Upgrades

  • Upgraded to v43.0.1 (#2004)

Co-authored-by: jackton1 17484350+jackton1@users.noreply.github.com (01e9662) - (tj-actions[bot])

43.0.1 - (2024-03-20)

🐛 Bug Fixes

  • Remove warning with detecting the local git repository when using Github's REST API (#2002) (077b23f) - (Tonye Jack)

📦 Bumps

... (truncated)

Commits

Dependabot compatibility score

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)

Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 43.0.1 to 44.0.0.
- [Release notes](https://github.com/tj-actions/changed-files/releases)
- [Changelog](https://github.com/tj-actions/changed-files/blob/main/HISTORY.md)
- [Commits](tj-actions/changed-files@20576b4...2d756ea)

---
updated-dependencies:
- dependency-name: tj-actions/changed-files
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Used by dependabot - identifies all PRs created by dependabot kind/misc Categorizes issue or PR as a miscellaneuous one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesnt merit a release note. labels Apr 1, 2024
@tekton-robot
Copy link
Collaborator

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 1, 2024
@vdemeester
Copy link
Member

/approve
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2024
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 2, 2024
@tekton-robot tekton-robot merged commit 71d03c8 into main Apr 2, 2024
13 checks passed
@dependabot dependabot bot deleted the dependabot/github_actions/tj-actions/changed-files-44.0.0 branch April 2, 2024 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dependencies Used by dependabot - identifies all PRs created by dependabot kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesnt merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants