In Gem hell migrating to RubyZip v1.0.0? Include zip-zip in your Gemfile and everything's coming up roses!
CI: test against Ruby 3.1
Format cookie 'Expires' timestamps as per RFC 2616
For reference:
Merge pull request #263 from orien/ruby-3.1
Format cookie Expires
timestamps as per RFC 2616
Remove Reel adapter
The Reel project is no-longer actively maintained and the GitHub repository has been archived.
CI: promote the Ruby 3.2 build step to non-experimental
Set gem homepage to current git repository
Add project metadata to the gemspec
As per https://guides.rubygems.org/specification-reference/#metadata, add metadata to the gemspec file. This'll allow people to more easily access the source code, raise issues and read the changelog. These bug_tracker_uri, changelog_uri, documentation_uri, homepage_uri, source_code_uri, and wiki_uri links will appear on the rubygems page at https://rubygems.org/gems/webmachine and be available via the Rubygems API after the next release.
Merge pull request #265 from orien/gem-metadata
Add project metadata to the gemspec
Merge pull request #264 from orien/remove-reel-adapter
Remove Reel adapter
Remove the HTTPkit adapter
The HTTPkit project seems not to be maintained:
Merge pull request #266 from orien/remove-httpkit-adapter
Remove dead links from the README
Both irwebmachine, and webmachine-sprockets have been abandoned.
Use a GitHub Actions build status badge in the readme document
Merge pull request #267 from webmachine/remove-dead-links
Remove dead links from the README
Merge pull request #268 from orien/ci-badge
Add the standardrb linter
standardrb provides a relaxed set of linting rules that provide the benefits of a linter without the headaches that can come from the slightly excessive rubocop defaults.
New rules we'd like to adopt can be enabled in
.rubocop.yml
, and similarly rules we don't want
to adopt can be disabled in .rubocop.yml
.
Apply rubocop rules (auto and manual fixes)
Add linter to CI
Drop 2.3, 2.4, and 2.5 from test build
These version of Ruby have reached EOL.
Remove duplicate 'rfc3986_percent_decode' method
Compare only the first lines of an error message
Separate args and keyword args
Fix zrem with array of integers (#256)
When using zrem with an integer like this zrem(@key, [11])
it did not
convert the member to a string and therefore did not remove the member
from the set.
Cut version 0.36.0 (#257)
RSpec: update configuration
RSpec: update specs using transpec
❯ transpec --convert example_group
Rubocop: resolve issues
CI: add Ruby 3.1 and 3.2 to the test matrix
CI: use ruby/setup-ruby action to install gems
CI: bump actions/checkout from 2 to 3
Resolves the warning: "Node.js 12 actions are deprecated."
Bump simplecov from 0.21 to 0.22
DELETE ME
Rubocop: resolve issues
Back in RSpec 2.11, a new expectation syntax was introduced. Check out the blog post that outlines the shortcomings of the should
syntax and how these are resolved with the new expect
syntax.
https://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
I propose the RSpec test suite be migrated to this expect
syntax. Luckily this is quite easy as there is a conversion tool that does all the heavy lifting: transpec.
I ran this tool across the test suite and this pull request consists of the changes.
DELETE ME
RSpec: update configuration
RSpec: update specs using transpec
❯ transpec --convert example_group
Fix zrem with array of integers (#256)
When using zrem with an integer like this zrem(@key, [11])
it did not
convert the member to a string and therefore did not remove the member
from the set.
Cut version 0.36.0 (#257)
Fix zrem with array of integers (#256)
When using zrem with an integer like this zrem(@key, [11])
it did not
convert the member to a string and therefore did not remove the member
from the set.
Cut version 0.36.0 (#257)
RSpec: update configuration
RSpec: update specs using transpec
❯ transpec --convert example_group
DELETE ME
RSpec: update configuration
RSpec: update specs using transpec
❯ transpec --convert example_group
DELETE ME
How about this?
Do we need this?
RSpec: fix matchers
RSpec: fix matchers
@ywen what do you think of this proposal?
Docker buildx v0.10.0 has been released and includes a number of nice features. It would be awesome to take advantage of these in our Buildkite pipelines!
Upgrade buildx from 0.9.1 to 0.10.1.
See the buildx release notes for details of the changes:
The dm-core and associated projects have been deprecated and their GitHub repositories archived. There hasn't been a new release since 2013!
The DataMapper code is not compatible with Ruby 3.2 and causes build failures for this project.
I propose the removal of the DataMapper integration.
Also included: run the test suite against Ruby 3.2 in CI.
CI: bump actions/checkout from 2 to 3
Resolves the warning: "Node.js 12 actions are deprecated."
CI: add Ruby 3.2 to the test matrix
Remove the DataMapper integration
The dm-core and associated projects have been deprecated and their GitHub repositories archived. There hasn't been a new release since 2013!
The DataMapper code is not compatible with Ruby 3.2 and causes build failures.
Let's remove the integration.