Skip to content

Release CI: Fix typo (maybe) #86

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bastelfreak
Copy link
Contributor

The last release failed with:

Run gem push --key github --host https://rubygems.pkg.github.com/openvoxproject *.gem
  gem push --key github --host https://rubygems.pkg.github.com/openvoxproject *.gem
  shell: /usr/bin/bash -e {0}
  env:
    RUBYGEMS_API_KEY: ***
    BUNDLE_GEM__PUSH_KEY: ***
    GEM_HOST_API_KEY: ***

Pushing gem to https://rubygems.pkg.github.com/openvoxproject...
Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured.
Error: Process completed with exit code 1.

And I guess that's because it's case sensitive, maybe?

The last release failed with:

```
Run gem push --key github --host https://rubygems.pkg.github.com/openvoxproject *.gem
  gem push --key github --host https://rubygems.pkg.github.com/openvoxproject *.gem
  shell: /usr/bin/bash -e {0}
  env:
    RUBYGEMS_API_KEY: ***
    BUNDLE_GEM__PUSH_KEY: ***
    GEM_HOST_API_KEY: ***

Pushing gem to https://rubygems.pkg.github.com/openvoxproject...
Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured.
Error: Process completed with exit code 1.
```

And I guess that's because it's case sensitive, maybe?
@rwaffen
Copy link
Member

rwaffen commented May 30, 2025

yes, repos have to be written in all lower. ran into the same problem with the containers

@bastelfreak
Copy link
Contributor Author

Did you read the diff correctly? It was all lower initially and failed.

smortex added a commit that referenced this pull request Jun 3, 2025
While here, adjust the GitHub registry URL to test the chages in #86.
smortex added a commit that referenced this pull request Jun 3, 2025
While here, adjust the GitHub registry URL to test the chages in #86.
smortex added a commit that referenced this pull request Jun 3, 2025
While here, adjust the GitHub registry URL to test the chages in #86.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants