Add --use-experimental-resolver flag.

[davidmorgan]

This makes it easier for me to compare, and for external users to try the new implementation before it's live.

@jakemac53 could you please help me figure out what I need to do with pubspec.yaml here?

It introduces new API in build_resolvers that is needed in build_runner, I tried bumping the dep but that obviously doesn't work because pub get fails on CI. Should I change to a path dependency until everything is released? Is there anything else I need to do / be aware of?

Thanks :)

[github-actions]

PR Health

Changelog Entry ✔️

Package	Changed Files

Changes to files need to be accounted for in their respective changelogs.

[jakemac53]

Should I change to a path dependency until everything is released? Is there anything else I need to do / be aware of?

I think you can just change the dependency to be ^2.4.4-wip so it matches the actual version in the pubspec. But then you need to remember to update that to ^2.4.4.

If this is for a package not in the pub workspace, then you will want a dependency override.

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:build	2.4.2	already published at pub.dev
package:build_config	1.1.2	already published at pub.dev
package:build_daemon	4.0.4	ready to publish	build_daemon-v4.0.4
package:build_modules	5.0.11	already published at pub.dev
package:build_resolvers	2.4.4-wip	WIP (no publish necessary)
package:build_runner	2.4.15-wip	WIP (no publish necessary)
package:build_runner_core	8.0.1-dev	ready to publish	build_runner_core-v8.0.1-dev
package:build_test	2.2.4-wip	WIP (no publish necessary)
package:build_web_compilers	4.1.1	already published at pub.dev
package:scratch_space	1.0.3-wip	WIP (no publish necessary)

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

[davidmorgan]

@jakemac53 done, PTAL :) thanks.