Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reset computed height based on full version string #239

Closed
wants to merge 1 commit into from
Closed

Reset computed height based on full version string #239

wants to merge 1 commit into from

Conversation

Kieranties
Copy link

Enables option to compare full version string when calculating height reset. This resolves issue: #198.

By adding the following property to version.json, the full version string is used for comparison during the calculation of the version height. The option requires explicit enablement to prevent breaking changes.

{
  "compareFullVersion": true
}

Enables option to compare full version string when calculating height reset
@Kieranties Kieranties changed the title Fixes #198 Reset computed height based on full version string Oct 25, 2018
@AArnott AArnott self-assigned this Oct 25, 2018
@Kieranties
Copy link
Author

@AArnott Do you have any feedback/guidance on this PR? I'm looking to start implementing builds soon and would love to have an official build supporting this.

@AArnott
Copy link
Collaborator

AArnott commented Nov 24, 2018

Looking now...

@AArnott
Copy link
Collaborator

AArnott commented Nov 24, 2018

There are some changes left to be made so that the answer is the same no matter which API is used. I'm working through it.

@AArnott
Copy link
Collaborator

AArnott commented Nov 24, 2018

I found a few inconsistencies around our support for {height} to appear anywhere other than the build number (3rd integer) position. I'm working my way through it, with tests.

@AArnott AArnott mentioned this pull request Nov 25, 2018
@AArnott
Copy link
Collaborator

AArnott commented Nov 25, 2018

Since the ultimate change for this includes breaking changes, your change is now part of a larger pull request that targets a new develop branch over at #256.

Thank you very much for getting this started, @Kieranties.

@AArnott AArnott closed this Nov 25, 2018
@Kieranties
Copy link
Author

Great stuff!

AArnott pushed a commit that referenced this pull request Apr 1, 2024
Bumps [xunit](https://github.com/xunit/xunit) from 2.6.2 to 2.6.3.
- [Commits](xunit/xunit@2.6.2...2.6.3)

---
updated-dependencies:
- dependency-name: xunit
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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