hyperprobe-agent 1.2.30.pre.3-java → 1.2.30.pre.4-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 88f9c8c2335d83637263aa097729a9376f7705e17ce97c29c6561a246d726e2d
-  data.tar.gz: 20c82b4d89fb6bebc8dea5572d9544b456eb4ea3693a3e9ed0b0d6b2a5bffb3a
+  metadata.gz: aa1f2bff34ff2f7edacc82c9efd63ac85dbcf228fc95c4ffdccbae468a44e4b6
+  data.tar.gz: 9ea2f101f232136bc519ec9d793d3d124c22a50df7b41cf848f094906b58038c
 SHA512:
-  metadata.gz: f4a292aacfc44780c07fc48e18754380e8c857d57a0f7953a65fb22002111a6df8828616964da6b1e513e1cb647a95c7b7820bfe158e396fe4e55abb05a0c905
-  data.tar.gz: 666037ce07525de8aa855f5cb85c0239b40a3964833daecc2c68d6157dc7334a4554916d04c87fbf9476c2542cd28ec777eb4efc026073c4e8dce9d6878f4ece
+  metadata.gz: '0861fd8586e04e93da1f7f90b2a997f5a50e03dca107481e40dde89dbe7023a3a6391f3546b73a4f0b8fdb26492d58903ccdd8455091ad272265c86f67ac9781'
+  data.tar.gz: 0d974f41d234968799df2952b23e97903519b4abad55149334a44a59b6376857f18dd1aca3c370ac45e016b014f519f896d7f808269872a4e6e9a5df13b65e3c

data/README.md

@@ -348,6 +348,8 @@ bash publish_rubygems.sh --dry-run
 
 This does not publish, but does build, may fetch Maven dependencies, and may update `Gemfile.lock`. `--version VERSION` (or the `VERSION` environment variable) also **writes `lib/hyperprobe/version.rb`**, including in a dry run; the standalone publisher does not restore these files. Publishing with `--yes` uploads both `pkg/hyperprobe-agent-VERSION.gem` and `pkg/hyperprobe-agent-VERSION-java.gem` at the same version. A failure on the second upload can leave the first artifact published; inspect both platforms before retrying. `--skip-tests` bypasses both runtime suites and is not a substitute for release validation.
 
+In GitHub Actions, the publisher obtains fresh RubyGems OIDC credentials immediately before upload (the job needs `id-token: write`). Locally it continues to use API keys from the documented environment variables or credential files. Dry runs never request publishing credentials. The root release uses `--upload-only --yes` to reuse the gems it already built and tested; this option still validates both packages, but must not be used without prior build/test validation.
+
 The root `build.sh` requires a clean worktree, checks both Ruby runtimes plus Maven/JDK tools before changing versions, and installs the MRI bundle before invoking the SDK validator. Bundler install output is suppressed to avoid leaking authenticated source URLs. On successful root builds, it restores only Ruby's tracked `lib/hyperprobe/version.rb` and `Gemfile.lock` when the Ruby version stage was entered. Failed builds retain the existing rollback behavior and can leave temporary versions/lockfile changes for inspection; unrelated rollback logic is unchanged. Do not use root `build.sh` for a Ruby-only check: it also builds other SDKs, Docker, and the extension, and `SHOULD_PUBLISH=yes` performs remote writes.
 
 Offline source/syntax checks that do not run the root build or publisher:
@@ -360,6 +362,8 @@ ruby -c Rakefile
 ruby -rrspec/core -e 'exit RSpec::Core::Runner.run(ARGV)' spec/release_integration_spec.rb
 ```
 
+The offline `spec/release_publish_spec.rb` and `spec/rubygems_oidc_spec.rb` also exercise CI authentication, local publishing, and failure handling with fake credentials and mocked HTTP/registry commands; they do not publish anything.
+
 The focused release checks require RSpec already installed, but not a built transport or a running demo/broker. Keep release credentials out of command arguments and logs; use the publisher's documented credential environment/file mechanisms.
 
 ## Local Demo Verification

data/lib/hyperprobe/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module HyperProbe
-  VERSION = '1.2.30.pre.3'
+  VERSION = '1.2.30.pre.4'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: hyperprobe-agent
 version: !ruby/object:Gem::Version
-  version: 1.2.30.pre.3
+  version: 1.2.30.pre.4
 platform: java
 authors:
 - Arif Khan