Skip to content

chore(release): set version to 0.0.0 - #10

Merged
ivanasabi merged 3 commits into
mainfrom
release/version-0.0.0
Jul 20, 2026
Merged

chore(release): set version to 0.0.0#10
ivanasabi merged 3 commits into
mainfrom
release/version-0.0.0

Conversation

@ivanasabi

Copy link
Copy Markdown
Contributor

Summary

Sets the package version to 0.0.0 in package.json and package-lock.json (root package entries only; the yocto-queue dependency entry that also reads 0.1.0 is left untouched).

Checklist

  • Commits are signed (git commit -S)
  • Commit messages follow Conventional Commits
  • Documentation has been updated (if needed)
  • The target branch follows the git flow model (main for release/hotfix PRs)
  • PRs targeting main have a release-type/... label or are intentionally marked skip-release
  • I have read and agree to the project's Code of Conduct
  • I have signed the Contributor License Agreement (CLA)

Additional context

Note: the release workflow computes the published version from CHANGELOG.md via keep-a-changelog-action (bump) and then runs npm version, so this manual 0.0.0 will be overwritten at release time by the bump result (base 0.0.0 + release-type label). Decide the release-type/... label (or skip-release) before merging.

@ivanasabi
ivanasabi requested a review from a team as a code owner July 20, 2026 11:17
@github-actions

Copy link
Copy Markdown

❗ This Pull Request will not trigger a release

A Pull Request with no release-type/... labels will not trigger a release, so you need to label this PR if you want to create a release.

@ivanasabi ivanasabi added the release-type/minor Minor version release label Jul 20, 2026
@github-actions

Copy link
Copy Markdown

❌ No CHANGELOG.md changes

No changes were found in CHANGELOG.md. Please update the Unreleased section with the changes that apply to this release.

@ivanasabi
ivanasabi force-pushed the release/version-0.0.0 branch from 3d24d76 to e5c3ffa Compare July 20, 2026 11:20
@github-actions

Copy link
Copy Markdown

🚀 Release Preview Success

You are going to release the version minor with the following changes:

0.1.0 - 2026-07-20

Added

  • Initial OSS repository shell.
  • Original code, including the diff highlighting plugin, and the example React application.

Changed

  • Set the package version to 0.0.0.

💡 Merge Strategy: Create a merge commit

Remember to use the 'Create a merge commit' strategy to merge this Pull Request (release/version-0.0.0main).

Set the package version to 0.0.0 in package.json and package-lock.json,
and record the change in the CHANGELOG Unreleased section.

Signed-off-by: Ivan Alvarez Sabin <ivanasabi@ext.inditex.com>
@ivanasabi
ivanasabi force-pushed the release/version-0.0.0 branch from e5c3ffa to dc29a0f Compare July 20, 2026 11:20
@github-actions

Copy link
Copy Markdown

🚀 Release Preview Success

You are going to release the version minor with the following changes:

0.1.0 - 2026-07-20

Added

  • Initial OSS repository shell.
  • Original code, including the diff highlighting plugin, and the example React application.

Changed

  • Set the package version to 0.0.0.

💡 Merge Strategy: Create a merge commit

Remember to use the 'Create a merge commit' strategy to merge this Pull Request (release/version-0.0.0main).

@github-actions

Copy link
Copy Markdown

🚀 Release Preview Success

You are going to release the version minor with the following changes:

0.1.0 - 2026-07-20

Changed

  • Initial OSS repository shell.
  • Original code, including the diff highlighting plugin, and the example React application.
  • Set the package version to 0.0.0.

💡 Merge Strategy: Create a merge commit

Remember to use the 'Create a merge commit' strategy to merge this Pull Request (release/version-0.0.0main).

@github-actions

Copy link
Copy Markdown

🚀 Release Preview Success

You are going to release the version minor with the following changes:

0.1.0 - 2026-07-20

Changed

  • Initial OSS repository shell.
  • Original code, including the diff highlighting plugin, and the example React application.

💡 Merge Strategy: Create a merge commit

Remember to use the 'Create a merge commit' strategy to merge this Pull Request (release/version-0.0.0main).

@ivanasabi
ivanasabi merged commit 1f9bac3 into main Jul 20, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-type/minor Minor version release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant