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

Was this repository recently moved? #980

Open
ellisio opened this issue May 10, 2024 · 19 comments
Open

Was this repository recently moved? #980

ellisio opened this issue May 10, 2024 · 19 comments
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.

Comments

@ellisio
Copy link

ellisio commented May 10, 2024

Thanks for stopping by to ask us a question! Please make sure to include:

  • What you're trying to do: Run releases using google-github-actions/release-please-action.
  • What code you've already tried: What we've been running.
  • Any error messages you're getting: This repo is now under googleapis/release-please-action. GitHub Actions does not follow redirects when resolving a uses 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.

@ellisio ellisio added priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue. labels May 10, 2024
@john-schroeder-volusion

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

I imagine many people will be searching for it shortly.

@ellisio
Copy link
Author

ellisio commented May 10, 2024

If ya'll want us to follow a "no release on Friday thing"... You could just ask.

@simon-connektica
Copy link

That's it, I'm done. I'm switching to Bing.

@zepeng811
Copy link

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 google-github-actions

@agrahamlincoln
Copy link

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

@sebmellen
Copy link

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 :)

@derekwinters
Copy link

FWIW, this will break release-please too. So at least the impact of this change will be felt internally too 😆

@gustavo-cycling
This comment was marked as a violation of GitHub Acceptable Use Policies
@DuncanCasteleyn
Copy link

DuncanCasteleyn commented May 13, 2024

Due to the move this action is no longer a verified action.

[Error] googleapis/release-please-action is not allowed to be used in redacted/workflows. Actions in this workflow must be: within a repository that belongs to your Enterprise account, created by GitHub, verified in the GitHub Marketplace, or matching the following: redacted.

@peterhirn
Copy link

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

@arunpgmi
Copy link

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

====================
##[debug]GitHub.DistributedTask.WebApi.UnresolvableActionDownloadInfoException: Unable to resolve action. Repository not found: google-github-actions/release-please-action
##[debug] at GitHub.Services.WebApi.VssHttpClientBase.HandleResponseAsync(HttpResponseMessage response, CancellationToken cancellationToken)
##[debug] at GitHub.Services.WebApi.VssHttpClientBase.SendAsync(HttpRequestMessage message, HttpCompletionOption completionOption, Object userState, CancellationToken cancellationToken)

@mkniewallner
Copy link

mkniewallner commented May 13, 2024

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.

@chgryan
Copy link

chgryan commented May 13, 2024

also getting this. any word?

Edit: sorry just reread the original post where we just need to point at the new googleapis/release-please-action

@jfklingler
Copy link

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 release-please-action's new forever home (for some definition of forever)?

@chingor13
Copy link
Contributor

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 google-github-actions organization as quickly as possible. However, please note that all future development will occur in the googleapis organization.

@ramonsnir
Copy link

@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.

@DuncanCasteleyn
Copy link

@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

unfunco added a commit to unfunco/anthropic-sdk-go that referenced this issue May 14, 2024
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)
unfunco added a commit to unfunco/anthropic-sdk-go that referenced this issue May 14, 2024
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)
unfunco added a commit to unfunco/terraform-aws-oidc-github that referenced this issue May 14, 2024
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)
unfunco added a commit to unfunco/terraform-aws-oidc-github that referenced this issue May 14, 2024
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)
unfunco added a commit to unfunco/chrome-ext-aws-saml-sts that referenced this issue May 14, 2024
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)
unfunco added a commit to unfunco/chrome-ext-aws-saml-sts that referenced this issue May 14, 2024
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)
unfunco added a commit to unfunco/chrome-ext-aws-saml-sts that referenced this issue May 14, 2024
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)
github-merge-queue bot pushed a commit that referenced this issue May 14, 2024
- 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
@meyuviofficial
Copy link

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.

@peterhirn
Copy link

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests