Skip to content

1.0.2#10

Merged
yosriady merged 3 commits into
mainfrom
release/1.0.2
Mar 27, 2026
Merged

1.0.2#10
yosriady merged 3 commits into
mainfrom
release/1.0.2

Conversation

@yosriady
Copy link
Copy Markdown
Collaborator

@yosriady yosriady commented Mar 27, 2026

@yosriady yosriady merged commit df9c26a into main Mar 27, 2026
5 checks passed
Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

Open in Devin Review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e25779be8f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

# Get the previous version tag (second most recent v* tag by version order)
# This is more reliable than using git describe which follows commit ancestry
CURRENT_TAG=${{ github.ref_name }}
PREV_TAG=$(git tag -l 'v*' --sort=-version:refname | grep -v "^${CURRENT_TAG}$" | head -1)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Select previous release tag from commit ancestry

Using git tag -l 'v*' --sort=-version:refname | ... | head -1 picks the highest-version non-current tag globally, not the nearest tag reachable from the release commit, so changelog generation can break when releasing an older hotfix tag while a newer major tag already exists. In that case PREV_TAG can become a descendant/unrelated tag (for example v2.0.0 when publishing v1.0.2), and git log ${PREV_TAG}..HEAD may produce an empty or incorrect commit list, resulting in misleading release notes.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request increments the package version from 1.0.1 to 1.0.2 in both package.json and package-lock.json. Additionally, it updates package.json to include repository metadata and publishing configurations for public access and provenance. I have no feedback to provide.

@yosriady yosriady deleted the release/1.0.2 branch March 27, 2026 07:06
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