Merge pull request #9 from taj54/release/v0.5.0

Release: v0.5.0

Author: taj54

.eslintrc.json

@@ -0,0 +1,8 @@
+{
+  "parser": "@typescript-eslint/parser",
+  "plugins": ["@typescript-eslint", "prettier"],
+  "extends": ["eslint:recommended", "plugin:@typescript-eslint/recommended", "prettier"],
+  "rules": {
+    "prettier/prettier": "error"
+  }
+}

.github/workflows/release.yml

@@ -6,7 +6,7 @@ on:
   workflow_dispatch:
 
 permissions:
-  contents: write  
+  contents: write
 
 jobs:
   release:
@@ -15,8 +15,7 @@ jobs:
       - name: Checkout code
         uses: actions/checkout@v5
         with:
-          fetch-depth: 0  
-      
+          fetch-depth: 0
 
       - name: Set up Git identity
         run: |
@@ -27,7 +26,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-            version: 10.13.1 
+          version: 10.13.1
 
       - name: Install deps
         run: pnpm install --frozen-lockfile
@@ -37,5 +36,3 @@ jobs:
 
       - name: Add build artifacts
         run: git add dist -f
-
-     

.github/workflows/tag-after-merge.yml

@@ -67,7 +67,7 @@ jobs:
         run: |
           # Match lines starting with "## vX.Y.Z " until the next "## "
           awk "/^## v${{ env.version }}[[:space:]]/{flag=1; next} /^## /{flag=0} flag" CHANGELOG.md > RELEASE_NOTES.md
-        
+
           echo "notes<<EOF" >> $GITHUB_ENV
           if [ "${{ env.release_type }}" = "major" ]; then
             echo "## 🚀 Major Release" >> $GITHUB_ENV
@@ -83,7 +83,7 @@ jobs:
         uses: softprops/action-gh-release@v2
         with:
           tag_name: v${{ env.version }}
-          name: "Release v${{ env.version }}"
+          name: 'Release v${{ env.version }}'
           body: ${{ env.notes }}
           make_latest: true
         env:

.github/workflows/version-bump.yaml

@@ -68,4 +68,4 @@ jobs:
       - name: Notify about Major Release (if major)
         if: inputs.release_type == 'major'
         run: |
-          echo "🚨 Major version update detected! Please review and merge manually."
+          echo "🚨 Major version update detected! Please review and merge manually."

.prettierrc.json

@@ -0,0 +1,7 @@
+{
+  "semi": true,
+  "trailingComma": "all",
+  "singleQuote": true,
+  "printWidth": 100,
+  "tabWidth": 2
+}

CHANGELOG.md

@@ -4,34 +4,32 @@ All notable changes for each version of the Ambient Music extension.
 
 ---
 
-## v0.4.0 2025 08 23
+## v0.5.0 2025 08 23
 
 -minor release
 
+## v0.4.0 2025 08 23
 
+-minor release
 
 ## v0.3.1 2025 08 23
 
 - refactor(release): move release creation to separate workflow
 
-
-
 ## v0.3.0 2025 08 23
 
 - ci: version bump updated
 - refactor: pnpm version updated
 - ci: pipeline improvement
 - fix: the version struct updated
 
-
-
 ## v0.2.1 2025 08 22
 
 - ci: add tag and release workflow
 - ci: automate release creation with release notes
 - feat: add php support
 - refactor: add multi-platform support
-- 
+
 ## v0.2.0 2025 08 22
 
 - ci: add tag and release workflow
@@ -78,7 +76,6 @@ All notable changes for each version of the Ambient Music extension.
 - ci path updated
 - feat: version bump minor release 0.1.0
 
-
 ## v0.1.0 2025 08 22
 
 - ci: Keep the versions up-to-date

CODE_OF_CONDUCT.md

@@ -17,24 +17,24 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-*   Demonstrating empathy and kindness toward other people
-*   Being respectful of differing opinions, viewpoints, and experiences
-*   Giving and gracefully accepting constructive feedback
-*   Accepting responsibility and apologizing to those affected by our mistakes,
-    and learning from the experience
-*   Focusing on what is best not just for us as individuals, but for the
-    overall community
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
 
 Examples of unacceptable behavior include:
 
-*   The use of sexualized language or imagery, and sexual attention or
-    advances of any kind
-*   Trolling, insulting or derogatory comments, and personal or political attacks
-*   Public or private harassment
-*   Publishing others' private information, such as a physical or email
-    address, without their explicit permission
-*   Other conduct which could reasonably be considered inappropriate in a
-    professional setting
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
 ## Enforcement Responsibilities
 

CONTRIBUTING.md

@@ -9,9 +9,11 @@ We love your input! We want to make contributing to this project as easy and tra
 - Becoming a maintainer
 
 ## We Develop with Github
+
 We use github to host code, to track issues and feature requests, as well as accept pull requests.
 
 ## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+
 Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
 
 1. Fork the repo and create your branch from `main`.
@@ -22,9 +24,11 @@ Pull requests are the best way to propose changes to the codebase. We actively w
 6. Issue that pull request!
 
 ## Any contributions you make will be under the MIT Software License
+
 In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http.://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
 
 ## Report bugs using Github's [issues](https://github.com/Taj/universal-version-bump/issues)
+
 We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!
 
 ## Write bug reports with detail, background, and sample code
@@ -39,13 +43,13 @@ We use GitHub issues to track public bugs. Report a bug by [opening a new issue]
 - What actually happens
 - Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
 
-People *love* thorough bug reports. I'm not even kidding.
+People _love_ thorough bug reports. I'm not even kidding.
 
 ## Use a Consistent Coding Style
 
-* 2 spaces for indentation rather than tabs
-* You can try running `pnpm run lint` for style unification
+- 2 spaces for indentation rather than tabs
+- You can try running `pnpm run lint` for style unification
 
 ## License
-By contributing, you agree that your contributions will be licensed under its MIT License.
 
+By contributing, you agree that your contributions will be licensed under its MIT License.

DEVELOPER.md

@@ -39,4 +39,4 @@ When you're ready to submit your changes, please follow these steps:
 3.  Push your changes to your forked repository.
 4.  Create a pull request to the `main` branch of this repository.
 
-We'll review your pull request as soon as possible. Thanks for your contribution!
+We'll review your pull request as soon as possible. Thanks for your contribution!

README.md

@@ -15,22 +15,22 @@ To use this action in your workflow, add the following step:
 - name: Bump version
   uses: taj54/[email protected]
   with:
-    release_type: "patch" # patch, minor, or major
+    release_type: 'patch' # patch, minor, or major
 ```
 
 ## Inputs
 
-| Name           | Description                                   | Default |
-| -------------- | --------------------------------------------- | ------- |
+| Name           | Description                                        | Default |
+| -------------- | -------------------------------------------------- | ------- |
 | `release_type` | Select the version bump type (patch, minor, major) | `patch` |
-| `git_tag`      | Whether to create a Git tag after bump        | `true`  |
+| `git_tag`      | Whether to create a Git tag after bump             | `true`  |
 
 ## Outputs
 
-| Name          | Description                            |
-| ------------- | -------------------------------------- |
-| `new_version` | The new bumped version                 |
-| `tag`         | The created Git tag (if enabled)       |
+| Name          | Description                      |
+| ------------- | -------------------------------- |
+| `new_version` | The new bumped version           |
+| `tag`         | The created Git tag (if enabled) |
 
 ## Example Workflow
 
@@ -52,7 +52,7 @@ jobs:
       - name: Bump version
         uses: taj54/[email protected]
         with:
-          release_type: "patch"
+          release_type: 'patch'
 ```
 
 ## Contributing
@@ -62,4 +62,3 @@ Contributions are welcome! Please see the [contributing guidelines](CONTRIBUTING
 ## License
 
 This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
-