-
Notifications
You must be signed in to change notification settings - Fork 207
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
Was this repository recently moved? #980
Comments
For reference, the error message we are seeing in our github action log is: I imagine many people will be searching for it shortly. |
If ya'll want us to follow a "no release on Friday thing"... You could just ask. |
That's it, I'm done. I'm switching to Bing. |
Can the maintainer clarify if this is an intended change and we can start updating the repo owner accordingly? (And the README for this repository should be updated) the worst case is we updated all our workflows and found out that the repo got moved back to the old owner |
I'm in the same position of @zepeng811 - I will gladly create a custom composite action that wraps this one to make it easier to manage this in the future, but I don't want to make any changes without knowing whether this will be reverted. This change clearly is causing widespread disruption so I'm hoping for some immediate guidance before I take action |
Nice work breaking all of our release workflows on a Friday afternoon! Really love knowing that we can rely on Google to be a stable partner :) |
FWIW, this will break release-please too. So at least the impact of this change will be felt internally too 😆 |
Due to the move this action is no longer a verified action.
|
fyi pinned actions seem to still work without issues (future renovate updates probably broken) jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: google-github-actions/release-please-action@a37ac6e4f6449ce8b3f7607e4d97d0146028dc0b # v4 |
For reference, the error message we are seeing in our github action log is: Error: Unable to resolve action. Repository not found: google-github-actions/release-please-action . Request you to fix the same ==================== |
It's a bit sad that GitHub Actions do not follow renaming like is done when cloning a repository, to not break old references. It may be on purpose, but since it might not be the case, I've opened a discussion about that: https://github.com/orgs/community/discussions/123611. |
also getting this. any word? Edit: sorry just reread the original post where we just need to point at the new |
Excellent demonstration of commit-and-run on a Friday afternoon. 👏 Can someone from Google please let us know for certain whether this was an oops and will be reverted or if this is indeed |
We sincerely apologize for the disruption caused by the repository move. We understand this has impacted your workflows and we deeply regret the inconvenience this has caused. The decision to move the repository was driven by internal organizational policies. We mistakenly assumed that GitHub's redirection mechanism, which typically works seamlessly for the UI and git operations, would also apply to actions. This was clearly an oversight on our part. We are working to restore a copy of the repository to the |
@chingor13 Note that the organization and the GitHub action lost their "verified" status on GitHub. This is an issue for some supply chain security tools, which use this as one layer out of many. |
I have created an issue to track the progress of the verfication #986 |
Google have moved the release-please-action from the google-github-actions organisation to the googleapis organisation. This GitHub issue comment states that future development will be done in the googleapis organisation. googleapis/release-please-action#980 (comment)
Google have moved the release-please-action from the google-github-actions organisation to the googleapis organisation. This GitHub issue comment states that future development will be done in the googleapis organisation. googleapis/release-please-action#980 (comment)
Google have moved the release-please-action from the google-github-actions organisation to the googleapis organisation. This GitHub issue comment states that future development will be done in the googleapis organisation. googleapis/release-please-action#980 (comment)
Google have moved the release-please-action from the google-github-actions organisation to the googleapis organisation. This GitHub issue comment states that future development will be done in the googleapis organisation. googleapis/release-please-action#980 (comment)
Google have moved the release-please-action from the google-github-actions organisation to the googleapis organisation. This GitHub issue comment states that future development will be done in the googleapis organisation. googleapis/release-please-action#980 (comment)
Google have moved the release-please-action from the google-github-actions organisation to the googleapis organisation. This GitHub issue comment states that future development will be done in the googleapis organisation. googleapis/release-please-action#980 (comment)
Google have moved the release-please-action from the google-github-actions organisation to the googleapis organisation. This GitHub issue comment states that future development will be done in the googleapis organisation. googleapis/release-please-action#980 (comment)
- I'm not the maintainer, but I thought I put a pr for updating the old organization name to the new one - related to: #980
As per out GitHub Org policies, all the non-verfied actions would be disabled by default. Do you have any timeline on the verification process? Because of this, I'm forced to use the CLI in the GitHub workflow. |
@meyuviofficial Just use a pinned action until this is re-verified jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: google-github-actions/release-please-action@e4dc86ba9405554aeba3c6bb2d169500e7d3b4ee # v4
id: release |
Thanks for stopping by to ask us a question! Please make sure to include:
google-github-actions/release-please-action
.googleapis/release-please-action
. GitHub Actions does not follow redirects when resolving auses
action. This has broken quite a bit of our deployment pipeline for many repos and orgs we've setup. Next time, we'll fork just to be safe, but if this was recently moved I'm not sure if you folks are aware of how this breaks GHA workflows. Ideally you should deprecate the old repository, and then fork to the new org, with documentation on where things will be released going forward.Edit: It's also worth noting, your README is not even updated to include this org name change, yet. So, I'm hoping this was a mistake and can be reverted.
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
The text was updated successfully, but these errors were encountered: