mathias-moreira/Salesforce CI Packager (2GP)
A GitHub Action that simplifies and automates the creation of Salesforce Second-Generation Packages (2GP)
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Mar 18, 2026
- License
- MIT
Pinned Snippet
uses: mathias-moreira/salesforce-ci-packager@b203ada42b372d53a8e10fece3a63a8f57c30264 # v3.1.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| auth-url | The URL of the Dev Hub org. This is used to create an auth file for the Dev Hub org. | yes | — |
| package-name | Name of the package to create a version of. | yes | — |
| target-dev-hub | Username or alias of the Dev Hub org. Not required if the `target-dev-hub` configuration variable is already set. | yes | — |
| package-type | The type of package to create. It can be either "Managed" or "Unlocked". | yes | — |
| packaging-directory | The directory containing the Salesforce project. If not specified, the action will run in the same directory as the action. | no | — |
| installation-key-bypass | Bypass the installation key requirement. (either --installation-key or --installation-key-bypass is required) If you bypass this requirement, anyone can install your package. | no | — |
| installation-key | Installation key for the package version. The default is null. Omit this flag if you specify --installation-key-bypass. | no | — |
| skip-validation | Skip validation during package version creation; you can't promote unvalidated package versions. Skips validation of dependencies, package ancestors, and metadata during package version creation. Skipping validation reduces the time it takes to create a new package version, but you can promote only validated package versions. Skipping validation can suppress important errors that can surface at a later stage. You can specify skip validation or code coverage, but not both. Code coverage is calculated during validation. | no | — |
| code-coverage | Calculate and store the code coverage percentage by running the packaged Apex tests included in this package version. Before you can promote and release a managed or unlocked package version, the Apex code must meet a minimum 75% code coverage requirement. We don't calculate code coverage for org-dependent unlocked packages or for package versions that specify --skip-validation. | no | — |
| async-validation | Return a new package version before completing package validations. Specifying async validation returns the package version earlier in the process, allowing you to install and test the new version right away. If your development team is using continuous integration (CI) scripts, async validation can reduce your overall CI run time. | no | — |
| timeout | Maximum time in minutes to wait for package creation to complete. Default is 60 minutes (1 hour). | no | — |
| polling-interval | Time in seconds between status check attempts. Default is 60 seconds (1 minute). | no | — |
| no-namespace | Create the package with no namespace; available only for unlocked packages. This flag is useful when you're migrating an existing org to packages. But use a namespaced package for new metadata. | no | — |
Outputs
| name | description |
|---|---|
| package-version-id | The package version id |
| package-version-number | The package version number |
| package-report | The package report |
| message | The message from the command execution |