Skip to content

[PDF-9974] ci: auto-publish to Artifactory on tag push - #166

Merged
YaroslavStryhun merged 1 commit into
masterfrom
PDF-9974-auto-publish-on-tag
Jul 24, 2026
Merged

YaroslavStryhun merged 1 commit into
masterfrom
PDF-9974-auto-publish-on-tag

Conversation

@YaroslavStryhun

@YaroslavStryhun YaroslavStryhun commented Jul 23, 2026 •

Copy link
Copy Markdown
Collaborator

What

Adds .github/workflows/publish-on-tag.yml — a thin caller that reuses the shared reusable workflow airslateinc/publish-composer-package/.github/workflows/workflow.yml@v1 to publish this package to Artifactory (composer-local) automatically whenever a new tag is pushed.

Why

Today a tag only lands in Artifactory after someone manually runs the Republish old tags to Artifactory action in airslateinc/everyday-automation. That is easy to forget. This automates it. See PDF-9974.

Notes

  • No code duplication — publish logic stays in the single shared reusable workflow; this repo only references it.
  • Uses the org COMPOSER_TOKEN secret.
  • The manual republish action is left untouched for back-fill / exceptional cases.

🤖 Generated with Claude Code

Add a caller workflow that reuses the shared
airslateinc/publish-composer-package reusable workflow to publish this
package to Artifactory (composer-local) whenever a new tag is pushed.
No publish logic is duplicated in this repo. The manual republish action
remains available for back-fill.

Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 23, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

@YaroslavStryhun, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e7e14630-bb0a-4cb1-a3c7-c668c5e9b65e

📥 Commits

Reviewing files that changed from the base of the PR and between 62dce2c and 8a7cbdd.

📒 Files selected for processing (1)
  • .github/workflows/publish-on-tag.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch PDF-9974-auto-publish-on-tag

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Snyk-Agent

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@YaroslavStryhun
YaroslavStryhun marked this pull request as ready for review July 23, 2026 14:17
@YaroslavStryhun
YaroslavStryhun requested a review from a team as a code owner July 23, 2026 14:17
@YaroslavStryhun
YaroslavStryhun merged commit 9a20e7b into master Jul 24, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants