gitlab-markup 2.2.0 → 2.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5c7d0b3c13484b4cd816732fcf490e181431fce66c88a28e3cd82116fa9201f5
-  data.tar.gz: b869c01afeeafacb2de6351c614342d74ac29251bebefe9136370df2bd4bcbc7
+  metadata.gz: 07fdbceaf3ac4c23eaf4e3b2ba3039d7128c442da418f70f5e46e37422ca692a
+  data.tar.gz: fc47174cd8dc2d3019acb9d9f1399b841d91b97818cb6040866a31dc8c5fbcf2
 SHA512:
-  metadata.gz: 1f5115eb4e4bcf451982b92ac03abefad485c8c5a4b20bd03b833b2e4e2b774effa01effc6813b847cbf0e25a753acb68588a17e3c8dac74643d2868542331f0
-  data.tar.gz: fa84dbc0162f161276dbd60effc8f4f2c3c894ca8cb44096401aaabf1794ff1ddf9a1ad6e472c60f4c19082a50d34e4d1f218414797a9e4511b60d02823656ba
+  metadata.gz: '0092c11fe007ff5dd6a9b0d321a54d918499fab4da110b0e65240f5fe6a96095c7c1e791737f1a9bc0fab069102f893be798f1cf343b6ab9f02aee8f44f7151d'
+  data.tar.gz: 6ee1e0614dacffd66279f9f5d2f625c5f4afd94b0d0fa1861e015d3795d0e52d5e5d5f2ab2ee274d3dbc57141e873f1733bb2fe3d3b606d1673bbf41757531b3

data/.gitlab-ci.yml

@@ -2,6 +2,10 @@ include:
   - template: SAST.gitlab-ci.yml  # https://gitlab.com/gitlab-org/gitlab-foss/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml
   - template: Security/Dependency-Scanning.gitlab-ci.yml # https://docs.gitlab.com/ee/user/application_security/dependency_scanning/
   - template: Security/Secret-Detection.gitlab-ci.yml # https://docs.gitlab.com/ee/user/application_security/secret_detection/
+  - component: gitlab.com/gitlab-org/components/gem-release/gem-release@~latest
+    inputs:
+      # The version is defined in lib/github-markup.rb, not the default lib/**/version.rb.
+      file_pattern_to_trigger_release: "lib/github-markup.rb"
 
 variables:
   LANG: "C.UTF-8"

data/CONTRIBUTING.md

@@ -72,16 +72,33 @@ If nothing complains, congratulations!
 
 ## Releasing a new version
 
+Releases are automated by the
+[`gem-release`](https://gitlab.com/gitlab-org/components/gem-release) CI/CD
+component configured in `.gitlab-ci.yml`.
+
 If you are the current maintainer of this gem:
 
-0. Bump the version number in `lib/github-markup.rb`, adhering to [Semantic Versioning](http://semver.org/)
-0. Update `HISTORY.md`
-0. Test the latest version on GitHub
-  0. Build the new version with `rake build`
-  0. Copy `pkg/gitlab-markup*.gem` to `vendor/cache` in your local checkout of GitHub
-  0. Update the version for `gitlab-markup` in the `Gemfile`
-  0. Run `bundle update --local gitlab-markup`
-  0. Run any relevant tests and test it manually from the browser.
-0. Push the new gem release with `rake release`. If you don't have permission to release to rubygems.org, contact one of the existing owners (`gem owners gitlab-markup`) and ask them to add you.
+1. Open a merge request that bumps `VERSION` in `lib/github-markup.rb`, adhering
+   to [Semantic Versioning](https://semver.org/). Update `HISTORY.md` in the same
+   merge request, and add a `Changelog:` trailer to the commit so the change
+   appears in the generated release notes.
+2. Once the merge request is merged to `master`, the pipeline detects the change
+   to `lib/github-markup.rb` and runs the release jobs automatically: it builds
+   the gem, creates a GitLab release, and publishes the gem to RubyGems.
+
+Notes:
+
+- Only edit `lib/github-markup.rb` to bump `VERSION`. Any change to it on
+  `master` triggers the release jobs, so a non-version edit would start a release
+  for a version that is already published; the `gem push` then fails, which is
+  harmless (nothing is re-published) but produces a red pipeline.
+- The release is tagged with the bare version (for example `2.3.0`). Tags created
+  before this automation was adopted used a `v` prefix (`v2.2.0`); older tags are
+  left as-is.
+- Release notes are generated from `Changelog:` commit trailers via the GitLab
+  changelog API. Commits without that trailer produce empty notes.
+- Publishing requires the `GEM_HOST_API_KEY` CI/CD variable (a RubyGems API key
+  with push access), restricted to protected branches. If you need push access to
+  RubyGems, contact one of the existing owners (`gem owners gitlab-markup`).
 
 [1]: https://gitlab.com/gitlab-org/gitlab-markup/merge_requests

data/HISTORY.md

@@ -1,5 +1,9 @@
 # History
 
+## 2.2.1 (2026-10-15)
+
+* [Add automated gem release pipeline using the gem-release CI component](https://gitlab.com/gitlab-org/ruby/gems/gitlab-markup/-/merge_requests/63)
+
 ## 2.2.0 (2026-10-15)
 
 * [Allow RDoc 8, require Ruby 3.2+](https://gitlab.com/gitlab-org/gitlab-markup/-/merge_requests/62)

data/lib/github-markup.rb

@@ -1,6 +1,6 @@
 module GitHub
   module Markup
-    VERSION = '2.2.0'
+    VERSION = '2.2.1'
     Version = VERSION
   end
 end

metadata

@@ -1,14 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: gitlab-markup
 version: !ruby/object:Gem::Version
-  version: 2.2.0
+  version: 2.2.1
 platform: ruby
 authors:
 - Chris Wanstrath
 - GitLab Engineering Team
+autorequire:
 bindir: bin
 cert_chain: []
-date: 1980-01-02 00:00:00.000000000 Z
+date: 2026-10-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -279,6 +280,7 @@ metadata:
   bug_tracker_uri: https://gitlab.com/gitlab-org/gitlab-markup/issues
   changelog_uri: https://gitlab.com/gitlab-org/gitlab-markup/blob/master/HISTORY.md
   source_code_uri: https://gitlab.com/gitlab-org/gitlab-markup
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -293,7 +295,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.7.2
+rubygems_version: 3.5.22
+signing_key:
 specification_version: 4
 summary: Fork from github-markup GitLab uses to render non markdown content
 test_files: