Skip to content

chore(ci): update minAppVersion to 1.12.7 and add git plugin to release #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ClaudiaFang merged 1 commit into from
Apr 26, 2026
Merged

chore(ci): update minAppVersion to 1.12.7 and add git plugin to release #18

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .releaserc.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,13 @@
"publishCmd": "zip -j git-files-sync-${nextRelease.version}.zip main.js manifest.json styles.css"
}
],
[
"@semantic-release/git",
{
"assets": ["manifest.json", "versions.json", "CHANGELOG.md", "package.json"],

@gemini-code-assist gemini-code-assist Bot Apr 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

When defining a custom assets list for the @semantic-release/git plugin, it overrides the default set. It is highly recommended to include package-lock.json (or your project's equivalent lockfile) to ensure it stays in sync with the version bump in package.json during releases. This prevents the repository from having an out-of-date lockfile after an automated release.

Suggested change
"assets": ["manifest.json", "versions.json", "CHANGELOG.md", "package.json"],
"assets": ["manifest.json", "versions.json", "CHANGELOG.md", "package.json", "package-lock.json"],

"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"

@gemini-code-assist gemini-code-assist Bot Apr 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

Including ${nextRelease.notes} in the commit message can lead to extremely large messages, especially for releases with many changes. This can clutter the git history and occasionally cause issues with git hooks or platform limits. Since the full release notes are already captured in CHANGELOG.md and on the GitHub release page, a more concise message is generally preferred.

Suggested change
"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
"message": "chore(release): ${nextRelease.version} [skip ci]"

}
],
[
"@semantic-release/github",
{
Expand Down
2 changes: 1 addition & 1 deletion manifest.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"id": "git-file-sync",
"name": "Git File Sync",
"version": "1.1.0",
"minAppVersion": "0.15.0",
"minAppVersion": "1.12.7",
"description": "Selectively sync individual notes with GitLab or GitHub. Push, pull, diff, and resolve conflicts — file by file, on mobile and desktop.",
"author": "ClaudiaFang",
"authorUrl": "https://github.com/ClaudiaFang",
Expand Down
Loading