-
Notifications
You must be signed in to change notification settings - Fork 210
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
Update analyzer to 1.0.0. #3003
Conversation
…unroll instructions
build_resolvers/CHANGELOG.md
Outdated
@@ -1,3 +1,7 @@ | |||
## 1.5.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## 1.5.4 | |
## 1.5.4-dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
@jcollins-g looks like we need another override on |
@jakemac53 yep, just figured that out myself. Trying again. Oddly enough, the problem won't reproduce locally. |
I think these tests don't run by default locally, they are tagged as "integration" tests and we exclude those by default locally as they take forever to run, you can do |
No, I was running them, just couldn't reproduce the problem. |
If this does manage to pass, the PR should be mergeable. PTAL. |
merging per offline discussion |
The following packages will need to be published in order to get #3003 into the ecosystem: ``` build build_config build_daemon build_modules build_resolvers build_runner build_runner_core build_test build_vm_compilers build_web_compilers ``` This PR adjusts the changelogs and version numbers to remove the `-dev` and so, get it ready to publish.
This sets the minimum constraint for analyzer on relevant packages to 1.0.0, and deals with the source_gen problem by commenting out json_serializable.
Also switches testing back to the dev branch, as this will now work with the new analyzer.