From 0f8e17e43f7d9edc0928d4311901e2ee390b0d1f Mon Sep 17 00:00:00 2001 From: Mederic Bazart Date: Tue, 17 Dec 2024 13:25:26 +0100 Subject: [PATCH] Bump v1.1.1 --- CHANGELOG.md | 4 ++++ README.md | 27 +++++++++++++++++++++++++++ etcd-discovery.gemspec | 2 +- 3 files changed, 32 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9d0cd91..4d9945b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,7 @@ +## v1.1.1 - 17 Dec 2024 + +* Fix Redacted credentials when printing services and hosts + ## v1.1.0 - 24 Aug 2023 * Setup Dependabot diff --git a/README.md b/README.md index 901a5b8..990c9a5 100644 --- a/README.md +++ b/README.md @@ -75,3 +75,30 @@ registration = EtcdDiscovery.register service, host registration.user # The current user (it can change at any time) registration.password # The current password (it can change at any time) ``` + +### Release a New Version +Bump new version number in: +- `CHANGELOG.md` +- `README.md` +- `etcd-discovery.gemspec` +Commit, tag and create a new release: + +```bash +version="1.1.1" + +git switch --create release/${version} +git add CHANGELOG.md README.md etcd-discovery.gemspec +git commit -m "Bump v${version}" +git push --set-upstream origin release/${version} +gh pr create --reviewer=leo-scalingo --title "$(git log -1 --pretty=%B)" +``` + +Once the pull request merged, you can tag the new release. + +```bash +git tag v${version} +git push origin master v${version} +gh release create v${version} +``` + +The title of the release should be the version number and the text of the release is the same as the changelog. diff --git a/etcd-discovery.gemspec b/etcd-discovery.gemspec index fa3a6a3..05dfdbd 100644 --- a/etcd-discovery.gemspec +++ b/etcd-discovery.gemspec @@ -1,6 +1,6 @@ Gem::Specification.new do |s| s.name = "etcd-discovery" - s.version = "1.1.0" + s.version = "1.1.1" s.summary = "Service discovery based on etcd" s.description = "Ruby implementation of a service discovery tool based on etcd" s.authors = ["Léo Unbekandt"]