Skip to content

chore(ci): bump publish workflow to v1.0.6 - #38

Merged
therajanmaurya merged 1 commit into
developmentfrom
chore/bump-publish-workflow-v1.0.6
Apr 29, 2026
Merged

chore(ci): bump publish workflow to v1.0.6#38
therajanmaurya merged 1 commit into
developmentfrom
chore/bump-publish-workflow-v1.0.6

Conversation

@therajanmaurya

@therajanmaurya therajanmaurya commented Apr 29, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Bumps publish-kmp-library.yml from @v1.0.5 to @v1.0.6
  • v1.0.6 adds automatic version resolution from Maven Central — no more duplicate version publish failures

Test plan

  • Trigger publish workflow manually and verify version is auto-resolved from Maven Central

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated the publishing workflow to use an improved version of the build and deployment process.

…entral)

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

coderabbitai Bot commented Apr 29, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

The publish GitHub Actions workflow has been updated to use a newer version of its reusable workflow dependency, changing the uses: reference from @v1.0.5 to @v1.0.6. All inputs and secrets configuration remain unchanged.

Changes

Cohort / File(s) Summary
Workflow Version Update
.github/workflows/publish.yml
Bumped reusable workflow reference from @v1.0.5 to @v1.0.6; all input configurations and secret wiring unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version bump so small and sweet,
From point-five to point-six complete,
The publish workflow springs to life,
With newer tools, no need for strife! 🚀

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main change: bumping the publish workflow to v1.0.6, which directly matches the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-publish-workflow-v1.0.6

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
Review rate limit: 0/1 reviews remaining, refill in 60 minutes.

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
.github/workflows/publish.yml (1)

28-28: Pin reusable workflow by commit SHA instead of mutable tag.

Using @v1.0.6 is convenient, but tags can be retargeted. For release/publish pipelines, pinning to the exact commit SHA is safer and more reproducible. Replace with: uses: MobileByteLabs/mbl-actionhub/.github/workflows/publish-kmp-library.yml@87d34544e815ca890157f0823231ab3c4f9bf657

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/publish.yml at line 28, Replace the reusable workflow
reference that currently uses the mutable tag
"MobileByteLabs/mbl-actionhub/.github/workflows/publish-kmp-library.yml@v1.0.6"
with the pinned commit SHA form
"MobileByteLabs/mbl-actionhub/.github/workflows/publish-kmp-library.yml@87d34544e815ca890157f0823231ab3c4f9bf657"
so the publish workflow is deterministic and cannot be retargeted; update the
`uses:` value in the publish.yml entry that references the reusable workflow
accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/workflows/publish.yml:
- Line 28: Replace the reusable workflow reference that currently uses the
mutable tag
"MobileByteLabs/mbl-actionhub/.github/workflows/publish-kmp-library.yml@v1.0.6"
with the pinned commit SHA form
"MobileByteLabs/mbl-actionhub/.github/workflows/publish-kmp-library.yml@87d34544e815ca890157f0823231ab3c4f9bf657"
so the publish workflow is deterministic and cannot be retargeted; update the
`uses:` value in the publish.yml entry that references the reusable workflow
accordingly.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c9fd25cb-94f9-4be5-a4de-3ffff9d4c848

📥 Commits

Reviewing files that changed from the base of the PR and between a7add63 and 523d991.

📒 Files selected for processing (1)
  • .github/workflows/publish.yml

@therajanmaurya
therajanmaurya merged commit ab97113 into development Apr 29, 2026
7 checks passed
@MobileByteLabsCommunity
MobileByteLabsCommunity deleted the chore/bump-publish-workflow-v1.0.6 branch April 29, 2026 11:13
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.

1 participant