-
Notifications
You must be signed in to change notification settings - Fork 13
Release for v1.111.5 #1140
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
Closed
Closed
Release for v1.111.5 #1140
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update CI config files for Launchable CLI v1 branch
It looks like c41d9a6 removed the `raise_for_status` check, without which error message from the server won't be reported, even as a warning. This breaks the subset call in case of the server failure, since `res.json()` looks as if it's returning an empty subset
[AIENG-196] Add the new command for the early flake detection
Release for v1.111.2
[chore] to display with pager
Extend --link flag to support explicit kinds
Fix CI on the v1 branch
Remove a useless test - HttpClientTest#test_reason
Release for v1.111.4
[chore] report an error in subset call
[AIENG-230] defined a switch to control the test selection behavior
df98d4b to
fe126f3
Compare
Contributor
|
@Konboi tagpr seems to be insisting to create a release against the main branch, even though |
Contributor
|
OTOH "files changed" is only listing two commits. Hmm... |
so, fixed the regexp to support groovy
The caller side was not removed. Oof.
…uild-provenance-2.x Update actions/attest-build-provenance action to v2.4.0
It looks like c41d9a6 removed the `raise_for_status` check, without which error message from the server won't be reported, even as a warning. This breaks the subset call in case of the server failure, since `res.json()` looks as if it's returning an empty subset
fe126f3 to
f36cb29
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request is for the next release as v1.111.5 created by tagpr. Merging it will tag v1.111.5 to the merge commit and create a GitHub release.
You can modify this branch "tagpr-from-v1.111.4" directly before merging if you want to change the next version number or other files for the release.
How to change the next version as you like
There are two ways to do it.
What's Changed
pipenvtouvby @ninjinkun in Migrate frompipenvtouv#1047launchabletosmart-testsby @ninjinkun in Rename fromlaunchabletosmart-tests#1059split-subsetandinspect testsby @ninjinkun in Removesplit-subsetandinspect tests#1063--branchoptional by @ninjinkun in Make--branchoptional #1089setup.cfgintopyproject.tomlby @ninjinkun in Migratesetup.cfgintopyproject.toml#1109--nameoptional inrecord commitcommand by @ninjinkun in Make--nameoptional inrecord commitcommand #1121mainby @ninjinkun in Release Smart Tests CLI intomain#1114Full Changelog: v1.111.4...v1.111.5