From feefe3ffa8ed3a1a49371306cccfd7e486701011 Mon Sep 17 00:00:00 2001 From: Hippolyte HENRY Date: Tue, 4 Feb 2020 17:18:51 +0100 Subject: [PATCH] Release 1.39.0 (#222) --- CHANGELOG.md | 11 +++++++++++ RELEASING.md | 38 ++++++++++++++------------------------ lib/dogapi/version.rb | 2 +- 3 files changed, 26 insertions(+), 25 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index fe3307d3..a6a4e48c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,16 @@ # Changes +## 1.39.0 / 2020-02-04 + +* [Added] Allow Setting Proxy without Using HTTP_PROXY, etc.. See [#180](https://github.com/DataDog/dogapi-rb/pull/180). Thanks [KingAlex42](https://github.com/KingAlex42). +* [Added] [capistrano] Add ability to use `etc.getpwuid` instead of `etc.getlogin` to get the user name. See [#146](https://github.com/DataDog/dogapi-rb/pull/146). Thanks [rkul](https://github.com/rkul). +* [Fixed] Check exit code of `hostname -f` for failures. See [#219](https://github.com/DataDog/dogapi-rb/pull/219). +* [Added] Add `validate_tags` util to check that `tags` is an array of strings. See [#218](https://github.com/DataDog/dogapi-rb/pull/218). +* [Added] Added function to deal with redirection of HTTP requests. See [#200](https://github.com/DataDog/dogapi-rb/pull/200). +* [Added] Add Synthetics support. See [#210](https://github.com/DataDog/dogapi-rb/pull/210). +* [Added] Add dashboard read_only option. See [#135](https://github.com/DataDog/dogapi-rb/pull/135). Thanks [tjoyal](https://github.com/tjoyal). +* [Added] Add options for force delete monitors. See [#213](https://github.com/DataDog/dogapi-rb/pull/213). + ## 1.38.0 / 2019-12-13 * [BUGFIX] Fix setting keys in both query params and headers. See [#194][] diff --git a/RELEASING.md b/RELEASING.md index 1c96320d..34567cce 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -1,5 +1,4 @@ # Releasing - This document summarizes the process of doing a new release of this project. Release can only be performed by Datadog maintainers of this repository. @@ -9,7 +8,6 @@ This project does not have a strict release schedule. However, we would make a r - Releases may be done more frequently than the above mentioned window. ## Prerelease checklist - * Check and upgrade dependencies where it applies and makes sense. - Create a distinct pull request and test your changes since it may introduce regressions. - While using the latest versions of dependencies is advised, it may not always be possible due to potential compatibility issues. @@ -18,39 +16,31 @@ This project does not have a strict release schedule. However, we would make a r - Locally and in the continuous integration system. * Manually test changes included in the new release. * Make sure documentation is up-to-date. -* [Update changelog](#update-changelog) - - Create a distinct pull request. - -## Update Changelog - -### Prerequisite - -- Install [datadog_checks_dev](https://datadog-checks-base.readthedocs.io/en/latest/datadog_checks_dev.cli.html#installation) using Python 3. - -### Commands - -- See changes ready for release by running `ddev release show changes .` at the root of this project. Add any missing labels to PRs if needed. -- Run `ddev release changelog . ` to update the `CHANGELOG.md` file at the root of this repository -- Commit the changes to the repository in a release branch and get it approved/merged. ## Release Process - ### Prerequisite - Install [bundler](https://bundler.io/) and setup your RubyGems credentials: 1. Register an account on https://rubygems.org/ -1. *Datadog Admins only* - Be assigned to Datadog's RubyGems gems by an owner*. +1. *Datadog Admins only* - Be assigned to Datadog's RubyGems gems by an owner. 1. Set a `~/.gem/credentials` file as the following: ``` --- :rubygems_api_key: $RUBYGEMS_APIKEY ``` +1. Install [datadog_checks_dev](https://datadog-checks-base.readthedocs.io/en/latest/datadog_checks_dev.cli.html#installation) using Python 3. -### Release +### Update Changelog +#### Commands +- See changes ready for release by running `ddev release show changes .` at the root of this project. Add any missing labels to PRs if needed. +- Run `ddev release changelog . ` to update the `CHANGELOG.md` file at the root of this repository +- Commit the changes to the repository in a release branch. Do not merge yet. -1. Tag the release with an annotated tag (based on your generated changelog), e.g.: `git tag -m"1.30" 1.30 `. -1. Update the gem version number in `lib/dogapi/version.rb`, create a PR and merge it. +### Release +1. Update the gem version number in `lib/dogapi/version.rb`, push it to your changelog PR. +1. Merge the PR to master. +1. Create the release in the [Github releases page](https://github.com/DataDog/dogapi-rb/releases). +1. Checkout the tag created at the previous step. 1. Build the gem: `bundle exec gem build dogapi.gemspec`. 1. Push the gem: `bundle exec gem push dogapi-x.x.x.gem`. -1. Create a release in the [Github releases page](https://github.com/DataDog/dogapi-rb/releases), it's ok to copy&paste from the changelog directly. -1. Check [Ruby Gem is published](https://rubygems.org/gems/dogapi). +1. Check that the [Ruby Gem is published](https://rubygems.org/gems/dogapi). +1. Bump the version again in `lib/dogapi/version.rb` to a dev version (e.g. `1.39.0` -> `1.40.0.dev`), open a PR and merge it to master. diff --git a/lib/dogapi/version.rb b/lib/dogapi/version.rb index 9b3f5ba1..0d1dfdfa 100644 --- a/lib/dogapi/version.rb +++ b/lib/dogapi/version.rb @@ -3,5 +3,5 @@ # Copyright 2011-Present Datadog, Inc. module Dogapi - VERSION = '1.38.0' + VERSION = '1.39.0' end