Skip to content

Releases: octokit/octokit.rb

v4.25.1

01 Jul 13:59
97ac5fb
Compare
Choose a tag to compare
  • Stop configuring Faraday's retry middleware twice (@Edouard-chin)
  • Fix various Ruby warnings (e.g. missing parentheses) (@coryf)

v4.25.0

15 Jun 20:58
Compare
Choose a tag to compare

✅ NOTE: This remediates A security advisory was published on versions 4.23.0 and 4.24.0 of this gem. You can read more about this in the published security advisory. ✅

DX Improvements

CI Improvements

Updates all build scripts to be more durable and adds details on how to run a manual file integrity check by @nickfloyd in #1446

Housekeeping

  • Drop support for Ruby 1.9.2 in Octokit::Client::Contents#create_contents by @timrogers in #1442

Full Changelog: v4.24.0...v4.25.0

v4.24.0

06 Jun 21:44
Compare
Choose a tag to compare

❗ NOTE: A security advisory has been published on version 4.24.0 of this gem. This gem was published with world-writeable files. You can read more about this in the published security advisory. ❗

Known issues

Note: This release fixes the issue around autoloading modules causing some modules to not load before use #1428


Code improvements


CI Improvements

  • Adds Code QL analysis to octokit.rb via @nickfloyd

Bug fixes


Full Changelog: v4.23.0...v4.24.0

v4.23.0

26 May 18:25
Compare
Choose a tag to compare

❗ NOTE: A security advisory has been published on version 4.23.0 of this gem. This gem was published with world-writeable files. You can read more about this in the published security advisory. ❗

Known issues

Autoloading modules cause some modules to not load before use

  • What: This version implements autoloading for some modules. The initial change was deemed good but our community has since come across issues where autoloading could cause issues due to modules not being loaded or load order even.
  • Action: We will be rolling back this change in the next release (#1428)
  • Next steps: This change provides value in the cases where this is not an issue so we are going to work to come up with an opt-in approach. More details here.
  • Work around: #1420

Hat tip to: @collinsauve. @waiting-for-dev, @etiennebarrie, and @timrogers for the discovery around this.


Code improvements


CI Improvements


Performance improvements


Bug fixes


Documentation


Full Changelog: v4.22.0...v4.23.0

v4.22.0

12 Jan 19:06
Compare
Choose a tag to compare

This version should be considered deprecated, and users should use or update to >= v4.23.0

Known issues

Issue
Faraday gemspec version is mismatched with implemented APIs and middleware.

Back in January 2022, with the v4.22.0 release Faraday 1.x features were added but we never updated the gemspec from '>= 0.9' to >=1 but we later released v4.23.0 with the correct version specified.

This is causing an issue because in the 4.22.0 changeset, we introduced middleware that uses 1.x faraday features but dependency resolution some cases still tries to use 0.9 and not 1.x

Resolution
This version is being marked as deprecated. Please update to update to >= v4.23.0 of the octokit.rb gem.

References:

#1392 | #1389

Deprecation Fix

Code Improvements

CI and dependency updates

Documentation

v4.21.0

26 Apr 19:11
1aff89c
Compare
Choose a tag to compare

API Support

Error handling

Code clean up

Documentation

v4.20.0

28 Dec 20:48
e214a28
Compare
Choose a tag to compare

API Support

Bug fixes

  • #1309 Paginate outside_collaborators calls @sds
  • #1316 Uses of FaradayMiddleware#on_complete should not be private @tarebyte

Code improvements

Documentation

v4.19.0

20 Oct 20:49
519512a
Compare
Choose a tag to compare

Code Improvements

API Support

Documentation

CI and dependency updates

v4.18.0

25 Mar 17:52
a201a5c
Compare
Choose a tag to compare

Documentation

Preview Header Support

Bug Fixes

v4.17.0

25 Mar 20:08
c5037e4
Compare
Choose a tag to compare

ATTENTION: This has release has known errors

In an effort to help users migrate to the new OAuth Applications API, a pull request was opened to update the existing endpoints: #1203.

Unfortunately the URLs for these endpoint changes were incorrect and were not caught as part of the test suite. In order to keep continuity we are keeping the release, but we have pulled this version from Rubygems.org.

Please update to v4.18.0 or above.

We apologize for the inconvenience this may have caused.