@tank/tank-package-publisher

To publish a package to the Tank registry, you can automate the process using a dedicated publisher workflow. It validates your skills.json manifest, enforces a dry-run-first workflow, and performs post-publish verification to ensure reliable releases.

Package publish validation fails when your skills.json manifest is invalid or package limits are exceeded. The publisher provides automated remediation for common errors like authentication issues, version conflicts, and exceeding file count or size limits.

Yes, you can test a package publish before sending it to the Tank directory. The workflow enforces a dry-run-first approach, allowing you to catch errors early and validate the skills.json manifest without executing the actual release.

To fix authentication and version conflict errors during package publishing, the workflow provides automated remediation. It identifies these common failures and offers specific fixes to ensure your skill package passes validation and publishes successfully.

Tank directory publishing enforces specific package size and file count limits to ensure registry stability. The validation phase checks your package against these constraints and provides automated remediation steps if the limits are exceeded.

Yes, the Tank publish workflow supports automated version bumping. It manages the entire publishing lifecycle, allowing you to increment package versions alongside authentication and post-publish verification for a reliable release process.