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

Use trusted gem publishing #223

Closed
kachick opened this issue Aug 28, 2024 · 8 comments
Closed

Use trusted gem publishing #223

kachick opened this issue Aug 28, 2024 · 8 comments
Assignees

Comments

@kachick
Copy link
Owner

kachick commented Aug 28, 2024

ref: kachick/ruby-ulid#544 (comment)

@kachick kachick self-assigned this Aug 28, 2024
@kachick kachick added this to 🛸 Aug 28, 2024
@github-project-automation github-project-automation bot moved this to 🙋‍♂ in 🛸 Aug 28, 2024
@kachick
Copy link
Owner Author

kachick commented Dec 26, 2024

> rake release
can not use rubocop in this environment
rspec-matchers-power_assert_matchers 0.3.0 built to pkg/rspec-matchers-power_assert_matchers-0.3.0.gem.
Tag v0.3.0 has already been created.
Pushing gem to https://rubygems.org...
You have enabled multi-factor authentication. Please visit https://rubygems.org/webauthn_verification/REDACTED to authenticate via security device. If you can't verify using WebAuthn but have OTP enabled, you can re-run the gem signin command with the `--otp [your_code]` option.
You are verified with a security device. You may close the browser window.
This API key cannot perform the specified action on this gem.

Both gem push pkg/rspec-matchers-power_assert_matchers-0.3.0.gem and rake release are failing even after passkey auth 🤔

Trusted gem publishing is enabled for all my gems?

@github-project-automation github-project-automation bot moved this from 🤷‍♂️ to 🎉 in 🛸 Dec 26, 2024
@kachick
Copy link
Owner Author

kachick commented Dec 26, 2024

@kachick
Copy link
Owner Author

kachick commented Dec 26, 2024

There are files that need to be committed first.

WHAT IS THIS

Run bundle exec rake release
  bundle exec rake release
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    RUBYGEMS_API_KEY: ***
    BUNDLE_GEM__PUSH_KEY: ***
    GEM_HOST_API_KEY: ***
    RUBYOPT: -r/home/runner/work/_actions/rubygems/release-gem/v1/rubygems-attestation-patch.rb 
rspec-matchers-power_assert_matchers 0.3.0 built to pkg/rspec-matchers-power_assert_matchers-0.3.0.gem.
rake aborted!
There are files that need to be committed first.

@kachick
Copy link
Owner Author

kachick commented Dec 26, 2024

💭 Eventually I should print debug with these problems, so hiding the git outputs by bundler is not happy... Should I inline as https://github.com/kachick/ruby-ulid/blob/1a592d74122039921e20b72231afaba52a0e4a91/.github/workflows/release.yml?

@kachick
Copy link
Owner Author

kachick commented Dec 26, 2024

4a512fc

Run git diff
diff --git a/.bundle/config b/.bundle/config
index 23[6](https://github.com/kachick/rspec-matchers-power_assert_matchers/actions/runs/12505150495/job/34888054129#step:4:7)9228..beed0f4 100644
--- a/.bundle/config
+++ b/.bundle/config
@@ -1,2 +1,2 @@
 ---
-BUNDLE_PATH: "vendor/bundle"
+BUNDLE_PATH: "/home/runner/work/rspec-matchers-power_assert_matchers/rspec-matchers-power_assert_matchers/vendor/bundle"

ruby/setup-ruby#576

😢

This way is useful for nix, but ...

@kachick
Copy link
Owner Author

kachick commented Dec 26, 2024

@kachick
Copy link
Owner Author

kachick commented Dec 27, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant