Skip to content

Comments

Expect additional optional version segment in version test.#1913

Merged
ioquatix merged 1 commit intorack:2-2-stablefrom
RubyElders:fix-version-spec
Jun 25, 2022
Merged

Expect additional optional version segment in version test.#1913
ioquatix merged 1 commit intorack:2-2-stablefrom
RubyElders:fix-version-spec

Conversation

@simi
Copy link
Contributor

@simi simi commented Jun 20, 2022

Last release (2.2.3.1) has added fourth segment of version string which wasn't expected by one test related to rackup -v. I have updated test to expect fourth (optional) segment.

CI fail was introduced by f705eac.

@ioquatix
Copy link
Member

@tenderlove just wondering if this was intentional in the sense that from what I can see, there has never been a security release in the past with a 4th version component.

@simi I'm assuming this breaks all stable branches with this test in place?

@simi
Copy link
Contributor Author

simi commented Jun 20, 2022

@simi I'm assuming this breaks all stable branches with this test in place?

Yes, it expects 3 segments in version. With this PR there could be optional fourth as well.

@ioquatix
Copy link
Member

@simi what I mean, is all stable 2.0, 2.1, 2.2 etc branches didn't expect a 4-component version?

@simi
Copy link
Contributor Author

simi commented Jun 20, 2022

@ioquatix this spec was introduced by eab436e.

by GitHub those are related versions: v2.2.2 v2.2.1 2.2.3.1 2.2.3 2.2.0

@ioquatix
Copy link
Member

I confirmed with @tenderlove that this is normative, so we will need to fix CI.

@ioquatix ioquatix merged commit e7c5b94 into rack:2-2-stable Jun 25, 2022
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.

2 participants