Ambiguous example for `registry_package` workflow trigger

[driimus]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

From https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#registry_package

For example, you can run a workflow when a package has been published.

could be updated to something more descriptive, such as:

For example, you can run a workflow when a new package version has been published.

It would also be helpful to further elaborate how the action types are triggered here:

• https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#package

What part(s) of the article would you like to see updated?

Given the description for action types of a registry_package event:

docs/data/reusables/webhooks/package_properties.md

Line 3 in 07f59b3

`action`|`string` | The action that was performed. Can be `published` or `updated`.

And the following example:

docs/content/actions/using-workflows/events-that-trigger-workflows.md

Line 1022 in 4263e05

For example, you can run a workflow when a package has been `published`.

I would've expected published to act as a trigger for a new npm registry package being created. The use case being running a script only once in a package monorepo for any newly created package.

Instead, the published action is dispatched whenever a new version of a package is published, which includes the behavior I would've expected for updated.

At this time I haven't been able to trigger updated actions to understand what differentiates it or what scenarios it supports. Perhaps another section of the docs that could be expanded.

Additional information

No response

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[steveward]

Thanks for the issue @driimus, I'll get this triaged for review.

[meetsussie]

Published...

[lucascosti]

👋 @driimus. Yep, you are correct in your understanding that published means any new release of the package. This could be an entirely new package, or any new package version.

Feel free for yourself (or anyone else) to open a PR to clarify the wording 🙂

[cmwilson21]

Looks like this one has been fixed. Closing the issue now 💛