Skip to content

Conversation

@stuartmorgan-g
Copy link
Collaborator

@stuartmorgan-g stuartmorgan-g commented Feb 23, 2023

Runs pub publish --dry-run on packages even when they have already been published, so that we will notice changes in pub publish behavior immediately.

This will unfortunately make publish-check take significantly longer for changes that affect the entire repo, since it will run validation for every package instead of essentially skipping all of them, but currently repo-checks are one of our fastest tasks so the impact should be minimal.

Also fixes violations found now that we are running it, where we had some git-ignored files checked in.

Fixes flutter/flutter#113788

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
  • I signed the CLA.
  • The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
  • I listed at least one issue that this PR fixes in the description above.
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
  • I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

Runs `pub publish --dry-run` on packages even when they have already
been published, so that we will notice changes in `pub publish` behavior
immediately.

This will unfortunately make `publish-check` take significantly longer
for changes that affect the entire repo, since it will run validation
for every package instead of essentially skipping all of them, but
currently repo-checks are one of our fastest tasks so the impact should
be minimal.

Fixes flutter/flutter#113788
@stuartmorgan-g stuartmorgan-g added override: no versioning needed Override the check requiring version bumps for most changes override: no changelog needed Override the check requiring CHANGELOG updates for most changes labels Feb 23, 2023
@stuartmorgan-g
Copy link
Collaborator Author

No changelog/version bumps needed for removing files that will be auto-generated anyway.

Copy link
Contributor

@gspencergoog gspencergoog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

32384589-a60f0e74-c078-11e7-9bc1-e5b5287aea9d

@stuartmorgan-g stuartmorgan-g added the autosubmit Merge PR when tree becomes green via auto submit App label Feb 23, 2023
@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Feb 23, 2023
@auto-submit
Copy link
Contributor

auto-submit bot commented Feb 23, 2023

auto label is removed for flutter/packages, pr: 3279, due to - The status or check suite android-platform_tests CHANNEL:master PACKAGE_SHARDING:--shardIndex 1 --shardCount 5 has failed. Please fix the issues identified (or deflake) before re-applying this label.

@stuartmorgan-g stuartmorgan-g added the autosubmit Merge PR when tree becomes green via auto submit App label Feb 27, 2023
@auto-submit auto-submit bot merged commit 7ebf1d4 into flutter:main Feb 27, 2023
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Feb 28, 2023
nploi pushed a commit to nploi/packages that referenced this pull request Jul 16, 2023
[tool] Always run publish check
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autosubmit Merge PR when tree becomes green via auto submit App override: no changelog needed Override the check requiring CHANGELOG updates for most changes override: no versioning needed Override the check requiring version bumps for most changes p: palette_generator platform-android

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Plugin tooling publishable can have out-of-band errors

2 participants