Point the release pipeline at the engines org
The publishing pipeline was already complete — subtree split to the mirror, gem build and push on a warp_engine-v* tag — but it had never been triggered, and after the org reorganization three of its targets were stale: the mirror push URL and the rubygems registry namespace (twice). The gemspec's allowed_push_host has to match the --host that `gem push` receives, so it now carries the full registry URL rather than the bare forge host, plus source and documentation links. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
+5
-1
@@ -13,7 +13,11 @@ Gem::Specification.new do |spec|
|
|||||||
|
|
||||||
spec.required_ruby_version = ">= 3.2"
|
spec.required_ruby_version = ">= 3.2"
|
||||||
|
|
||||||
spec.metadata["allowed_push_host"] = "https://git.teletypegames.org"
|
# Must match the --host passed to `gem push`; the forge serves one RubyGems
|
||||||
|
# registry per org, and the engine lives in `engines`.
|
||||||
|
spec.metadata["allowed_push_host"] = "https://git.teletypegames.org/api/packages/engines/rubygems"
|
||||||
|
spec.metadata["source_code_uri"] = "https://git.teletypegames.org/engines/warp_engine"
|
||||||
|
spec.metadata["documentation_uri"] = "https://wiki.teletypegames.org/infrastructure/warp-engine"
|
||||||
|
|
||||||
spec.files = Dir["{app,config,db,lib}/**/*", "README.md"]
|
spec.files = Dir["{app,config,db,lib}/**/*", "README.md"]
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user