update the publishing script (#232)
diff --git a/.github/workflows/publish.yaml b/.github/workflows/publish.yaml
index ef785c7..fcb7ccb 100644
--- a/.github/workflows/publish.yaml
+++ b/.github/workflows/publish.yaml
@@ -11,4 +11,4 @@
jobs:
publish:
if: ${{ github.repository_owner == 'dart-lang' }}
- uses: devoncarew/firehose/.github/workflows/publish.yaml@main
+ uses: dart-lang/ecosystem/.github/workflows/publish.yaml@main
diff --git a/README.md b/README.md
index 33c2b00..379893b 100644
--- a/README.md
+++ b/README.md
@@ -443,25 +443,10 @@
[ia32] Intel x86
```
-## Contributions, PRs, and publishing
+## Publishing automation
-When contributing to this repo:
-
-- if the package version is a stable semver version (`x.y.z`), the latest
- changes have been published to pub. Please add a new changelog section for
- your change, rev the service portion of the version, append `-dev`, and update
- the pubspec version to agree with the new version
-- if the package version ends in `-dev`, the latest changes are unpublished;
- please add a new changelog entry for your change in the most recent section.
- When we decide to publish the latest changes we'll drop the `-dev` suffix
- from the package version
-- for PRs, the `Publish` bot will perform basic validation of the info in the
- pubspec.yaml and CHANGELOG.md files
-- when the PR is merged into the main branch, if the change includes reving to
- a new stable version, a repo maintainer will tag that commit with the pubspec
- version (e.g., `v1.2.3`); that tag event will trigger the `Publish` bot to
- publish a new version of the package to pub.dev
-
+For information about our publishing automation and release process, see
+https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.
[posix]: https://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap12.html#tag_12_02
[gnu]: https://www.gnu.org/prep/standards/standards.html#Command_002dLine-Interfaces
