Upload a package and publish new versions

You publish by uploading a .tgz file of your package folder. The Marketplace checks it immediately.

Prepare the file

• Put pgb.package.json at the top of the folder (or inside one folder).
• An optional README.md becomes the package's About this package text.
• Do not include symbolic links, .env files, keys or passwords. Secret-looking strings (such as private keys and common token formats) reject the package.
• Limits: 50 MB for the file, 200 MB unpacked, 20 MB per file, 5,000 files, and paths up to 240 characters and 20 folders deep. Only gzip is accepted.

Upload

1. Open Publish and choose Upload a package.
2. Under Package file (.tgz, up to 50 MB), choose your file.
3. Choose Upload and check.

You must be a member of the publisher named in the file. Create one first if needed. See Become a publisher.

Read the result

• Not accepted. A list under What to fix names every problem and, where it applies, the file it is in. Fix them and upload again.
• Accepted. You see " was accepted", a status pill and the size. Listed means it is live. Pending review means it is unlisted until PGB approves it. Choose Manage this package or View listing.

Publish a new version

Published versions never change. To fix or improve a package, raise version in the manifest (1.0.1, 1.1.0, 2.0.0), build a new .tgz and upload it the same way. A version number can never be reused, even after it is yanked.

Check your listing

On Manage this package you can edit the display name, summary, up to five categories, tags (up to 10) and Visibility: Public (listed once approved) or Private (only your team). See Review, yank, deprecate and report.

Good to know

• Test your template in Studio with a version number before publishing it widely.
• Dependencies must exist and be satisfiable, or the upload is rejected.
• Packages from independent publishers that ask for sensitive permissions or include executable code wait for review.