Skip to content

[Version] Make hash based upon canonical segments#1659

Merged
homu merged 1 commit intomasterfrom
seg-canonical-segments
Jul 19, 2016
Merged

[Version] Make hash based upon canonical segments#1659
homu merged 1 commit intomasterfrom
seg-canonical-segments

Conversation

@segiddins
Copy link
Copy Markdown
Contributor

Description:

Closes #1617.
This makes sure the hash reflects a canonical_segments property, which just removes trailing 0s from the numeric and pre-release segments as <=> does

Tasks:

  • Describe the problem / feature
  • Write tests
  • Write code to solve the problem
  • Get code review from coworkers / friends
  • Squash commits

I will abide by the code of conduct.

@segiddins
Copy link
Copy Markdown
Contributor Author

Failing because the bundler submodule needs to be updated to include a fix that accounts for the release of rack 2

@segiddins segiddins force-pushed the seg-canonical-segments branch from 4492166 to 15ca22f Compare July 15, 2016 18:15
@indirect
Copy link
Copy Markdown

@homu r+

@homu
Copy link
Copy Markdown
Contributor

homu commented Jul 19, 2016

📌 Commit 15ca22f has been approved by indirect

homu added a commit that referenced this pull request Jul 19, 2016
[Version] Make hash based upon canonical segments

# Description:

Closes #1617.
This makes sure the hash reflects a `canonical_segments` property, which just removes trailing 0s from the numeric and pre-release segments as `<=>` does

# Tasks:

- [ ] Describe the problem / feature
- [ ] Write tests
- [ ] Write code to solve the problem
- [ ] Get code review from coworkers / friends
- [ ] [Squash commits](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)

I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md).
@homu
Copy link
Copy Markdown
Contributor

homu commented Jul 19, 2016

⌛ Testing commit 15ca22f with merge c134d46...

@homu
Copy link
Copy Markdown
Contributor

homu commented Jul 19, 2016

☀️ Test successful - status

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants