agentforge-telegram-notifier 0.2.0 → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +6 -0
  3. data/README.md +3 -3
  4. data/RUBYGEMS-PUBLISHING.md +12 -27
  5. data/lib/agentforge/telegram_notifier.rb +1 -1
  6. metadata +6 -6
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 86111d98f4d117f828ff82b987574b148507cb8b6ad002baf19b449816ca9f69
4
- data.tar.gz: 91daa1fd2a11d485ea0ae63a8e55ca5df4f29b9e682e5df0e4848e38669447db
3
+ metadata.gz: ac681429cfe94a0cd828e4895f934a68d1d975bad321475e291b4253a52b32ee
4
+ data.tar.gz: bd5e45a28e349097a890c2e5bd36050a25397df98963f3db1d70c4fbc83475e2
5
5
  SHA512:
6
- metadata.gz: 1bbc0813bed9f17ce98fa95542142164d41828955dbf0c0c5877a2f239a46b775acef7692903c0a9c982c38affe9433156e09f9dc3af1ccec980425cf2276683
7
- data.tar.gz: a138efb042e8a3ca54916bf81a39cce49a68a4d211e0d7c8ae08110ae51237ba89c1f4f5c0122dfbc0e92e1dbd9db9604b98ce106b07a96d9755b6a969f5e1fa
6
+ metadata.gz: fea928cd2aaad525d3426c98b0061a1bc0e3ae8e5b84366ccd20f9b8cf0c8105d88bd0f4e03613ddd65d7e4c499e6666176e25898c1ac4fb410aea27fbad80a9
7
+ data.tar.gz: 36e92a2726684e3ac849b467310f1f9ef263db66fa2760fc6ab5e62153a219f41497d173bbaf8ed7fbf655cbf55720704b57aeeceaedb56328d7544c357bd5aa
data/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.2.1
4
+
5
+ - Public Ruby SDK source and documentation are available in AgentForge-Labs/telegram-notifier-distributions.
6
+ - RubyGems homepage, source, documentation and issue links now resolve anonymously without exposing the commercial backend.
7
+ - No runtime API or authentication changes.
8
+
3
9
  ## 0.2.0
4
10
 
5
11
  - Migrated the Ruby package identity to `agentforge-telegram-notifier`.
data/README.md CHANGED
@@ -1,11 +1,11 @@
1
1
  # agentforge-telegram-notifier for Ruby
2
2
 
3
- Official Ruby client for the **Telegram Notifier public v1 API**. The source lives in
4
- this monorepo under `sdk/ruby`; no separate Ruby repository is required.
3
+ Official Ruby client for the **Telegram Notifier public v1 API**. The reviewed public source is available at
4
+ https://github.com/AgentForge-Labs/telegram-notifier-distributions/tree/main/sdk/ruby; the upstream commercial monorepo remains private.
5
5
 
6
6
  ## Install
7
7
 
8
- After the RubyGems release is activated:
8
+ Published on RubyGems.org:
9
9
 
10
10
  ```bash
11
11
  gem install agentforge-telegram-notifier
data/RUBYGEMS-PUBLISHING.md CHANGED
@@ -1,35 +1,20 @@
1
1
  # RubyGems publishing
2
2
 
3
- Canonical gem: `agentforge-telegram-notifier`.
3
+ Canonical RubyGems gem: agentforge-telegram-notifier.
4
4
 
5
- Source remains in the
6
- `AgentForge-Labs/telegram-notifier-public_commercial` monorepo under `sdk/ruby`.
7
- Do not create or sync a separate Ruby source repository.
5
+ The reviewed sdk/ruby source originates in the private AgentForge-Labs/telegram-notifier-public_commercial monorepo and is exported only after an explicit allowlist review to the public distribution repository:
6
+ https://github.com/AgentForge-Labs/telegram-notifier-distributions/tree/main/sdk/ruby
8
7
 
9
- ## Release
8
+ ## Release process
10
9
 
11
- The `rubygems-release` workflow accepts an explicit stable `X.Y.Z` version or the
12
- `telegram-notifier-ruby-vX.Y.Z` tag.
10
+ The rubygems-release.yml workflow accepts exact X.Y.Z or telegram-notifier-ruby-vX.Y.Z tags. Both gemspec and internal Ruby VERSION must match.
13
11
 
14
- Before publication it:
12
+ 1. Verify the canonical version and public/private artifact boundary.
13
+ 2. Run Ruby unit tests and public v1 API conformance.
14
+ 3. Build the gem with isolated pinned Ruby 3.3.12 on the Netcup long runner.
15
+ 4. Authenticate through the permanent RubyGems Trusted Publisher OIDC binding for the private upstream, rubygems-release.yml and environment rubygems.
16
+ 5. Publish to RubyGems and verify a fresh public registry install (PUBLIC_RUBYGEMS_INSTALL=PASS).
15
17
 
16
- 1. verifies the gem version,
17
- 2. runs Ruby unit tests and Telegram Notifier public-v1 conformance,
18
- 3. builds the exact gem,
19
- 4. verifies the thin distribution boundary,
20
- 5. installs the built gem in an isolated Ruby container.
18
+ The official RubyGems configure-rubygems-credentials action is pinned to immutable v2.1.0 commit dc5a8d8553e6ee01fc26761a49e99e733d17954a. Interactive account credentials remain in the encrypted MCP publisher vault, not the code or CI. If publication or public registry install cannot be verified, release fails closed. The CI runner never receives production Docker daemon permissions.
21
19
 
22
- Publication uses RubyGems GitHub OIDC Trusted Publishing via
23
- `rubygems/configure-rubygems-credentials@v2` in the protected `rubygems` environment.
24
- The account owner must configure the matching pending trusted publisher for
25
- `AgentForge-Labs/telegram-notifier-public_commercial` and
26
- `rubygems-release.yml`. The interactive account password stays in the
27
- encrypted MCP publisher vault, not in this repository or its CI inputs.
28
- If RubyGems cannot authorize the OIDC identity, publication fails closed.
29
-
30
- After a push, the workflow installs the exact public version from RubyGems and requires
31
- `PUBLIC_RUBYGEMS_INSTALL=PASS`.
32
-
33
- At migration time the canonical gem page returned 404, so this repository does not
34
- claim that public publication already happened. The former legacy gem identity is
35
- retired from this workflow and must not receive new releases.
20
+ Export public source before publishing and keep a source tag for each immutable gem release. Do not expose the hosted backend or private monorepo.
data/lib/agentforge/telegram_notifier.rb CHANGED
@@ -9,7 +9,7 @@ require "uri"
9
9
 
10
10
  module AgentForge
11
11
  module TelegramNotifier
12
- VERSION = "0.2.0"
12
+ VERSION = "0.2.1"
13
13
  DEFAULT_ORIGIN = "http://127.0.0.1:8818"
14
14
  USER_AGENT = "agentforge-telegram-notifier/#{VERSION} ruby"
15
15
  RETRYABLE = [429, 502, 503, 504].freeze
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: agentforge-telegram-notifier
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.0
4
+ version: 0.2.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - AgentForge Labs
@@ -25,14 +25,14 @@ files:
25
25
  - RUBYGEMS-PUBLISHING.md
26
26
  - lib/agentforge-telegram-notifier.rb
27
27
  - lib/agentforge/telegram_notifier.rb
28
- homepage: https://github.com/AgentForge-Labs/telegram-notifier-public_commercial
28
+ homepage: https://github.com/AgentForge-Labs/telegram-notifier-distributions
29
29
  licenses:
30
30
  - AGPL-3.0-only
31
31
  metadata:
32
- homepage_uri: https://github.com/AgentForge-Labs/telegram-notifier-public_commercial
33
- source_code_uri: https://github.com/AgentForge-Labs/telegram-notifier-public_commercial
34
- bug_tracker_uri: https://github.com/AgentForge-Labs/telegram-notifier-public_commercial/issues
35
- documentation_uri: https://github.com/AgentForge-Labs/telegram-notifier-public_commercial/blob/main/sdk/ruby/README.md
32
+ homepage_uri: https://github.com/AgentForge-Labs/telegram-notifier-distributions
33
+ source_code_uri: https://github.com/AgentForge-Labs/telegram-notifier-distributions
34
+ bug_tracker_uri: https://github.com/AgentForge-Labs/telegram-notifier-distributions/issues
35
+ documentation_uri: https://github.com/AgentForge-Labs/telegram-notifier-distributions/blob/main/sdk/ruby/README.md
36
36
  post_install_message:
37
37
  rdoc_options: []
38
38
  require_paths: