-
Notifications
You must be signed in to change notification settings - Fork 17
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
bastelfreak
wants to merge
1
commit into
OpenVoxProject:main
Choose a base branch
from
bastelfreak:typo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or 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
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?
yes, repos have to be written in all lower. ran into the same problem with the containers |
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.
ekohl
approved these changes
Jun 10, 2025
@@ -28,7 +28,7 @@ jobs: | |||
echo ":github: Bearer ${{ secrets.GITHUB_TOKEN }}" >> ~/.gem/credentials | |||
chmod 0600 ~/.gem/credentials | |||
- name: Publish gem to GitHub packages | |||
run: gem push --key github --host https://rubygems.pkg.github.com/openvoxproject *.gem | |||
run: gem push --key github --host https://rubygems.pkg.github.com/OpenVoxProject *.gem |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it a good idea to make it a variable to avoid hardcoding it?
Suggested change
run: gem push --key github --host https://rubygems.pkg.github.com/OpenVoxProject *.gem | |
run: gem push --key github --host https://rubygems.pkg.github.com/${{ github.repository_owner }} *.gem |
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.
The last release failed with:
And I guess that's because it's case sensitive, maybe?