Do not ask to publish from main

This apparently isn't needed now.

Author: horgh

README.dev.md

@@ -3,20 +3,20 @@ Steps for releasing:
 1. Review open issues and PRs to see if any can easily be fixed, closed, or
    merged.
 2. Bump copyright year in `README.md`, if necessary.
-3. Review `CHANGELOG.md` for completeness and correctness. Update its
+3. Consider whether any dependencies need to be updated.
+4. Review `CHANGELOG.md` for completeness and correctness. Update its
    release date.
-4. Set the version in `package.json`.
-5. Create a release PR containing the updates relating to any of the steps
+5. Set the version in `package.json`.
+6. Run `npm publish`. You can do this from the release branch. This will
+   generate the docs, deploy docs, and publish the module to NPM.
+7. Create a release PR containing the updates relating to any of the steps
    above.
-6. Ensure that the release PR is merged into `main`.
-7. With `main` checked out, run `npm publish`. This will generate the
-   docs, deploy docs, and publish the module to NPM.
 8. Create and push a git tag (eg `git tag v4.2.0 && git push --tags`).
-8. Manually create a release on GitHub to include the release-specific
+9. Manually create a release on GitHub to include the release-specific
    notes found in `CHANGELOG.md`.
-9. Verify the release on
-   [GitHub](https://github.com/maxmind/minfraud-api-node/releases) and
-   [NPM](https://npmjs.com/package/@maxmind/minfraud-api-node).
+10. Verify the release on
+    [GitHub](https://github.com/maxmind/minfraud-api-node/releases) and
+    [NPM](https://npmjs.com/package/@maxmind/minfraud-api-node).
 
 ## Set up pre-commit hooks