[ADDED] Note about the limitation of workflow triggering

To ensure that workflows triggered by a bot (like github-actions[bot]) do not get stuck or require manual approval, you need to make the bot a member of your repository or organization. Here's how you can do this:

---

## 1. For GitHub Apps (like Dependabot or a custom bot)

- **Install the GitHub App** (e.g., Dependabot, Renovate) directly into your repository or organization.
- Go to your repository → Settings → Integrations → GitHub Apps, and click "Configure" or "Install."
- Select the repositories or the entire organization where you want the app to have access.
- Once installed, the app will act as a member, and workflow runs it triggers will not require manual approval.

---

## 2. For Personal Access Token Bots or Service Accounts

If you use a bot account (a separate GitHub user with a PAT):

1. **Invite the bot user** to your repository or organization:
   - Go to your repo → Settings → Collaborators and teams.
   - Click "Add people" and invite the bot's GitHub username.
   - Assign at least "Write" access (higher, if needed).

2. **Accept the invitation** using the bot account.

3. **Configure your workflows or automation** to use this bot's credentials (e.g., via secrets).

---

## 3. For github-actions[bot] (default GitHub Actions bot)

- You **cannot add** github-actions[bot] as a member. This bot represents workflow runs triggered by GitHub Actions itself.
- To avoid manual approval for this bot:
  - Set your "Approval for running fork pull request workflows" setting to either:
    - "Require approval for first-time contributors" (after first PR, future PRs run automatically)
    - OR "Require approval for first-time contributors who are new to GitHub" (least restrictive)
  - **Option 3** ("Require approval for all external contributors") will always require manual approval for github-actions[bot], since it cannot be made a member.

---

## 4. For Organization Bots

- If you use a bot as part of your organization (like a custom automation user):
  - Invite the bot to your organization.
  - Add it to the repository as a member or team member.

---

### Summary Table

| Bot Type                  | Add as Member Possible? | How to Avoid Approval Requirement           |
|---------------------------|------------------------|---------------------------------------------|
| GitHub App (e.g. Dependabot) | Yes                    | Install app to repo/org                     |
| Custom GitHub User Bot    | Yes                    | Invite as collaborator/org member           |
| github-actions[bot]       | No                     | Use less restrictive workflow approval mode |

---

**Bottom Line:**
For github-actions[bot], you can’t add it as a member—just adjust the workflow approval settings as needed. For other bots, invite them as collaborators or install them as apps.

If you tell me which specific bot you’re using, I can give more targeted instructions!

.github/workflows/version-management.yml

@@ -3,6 +3,10 @@
 # 
 # 🔍 TIP: Run `scripts/show_version_info.sh` locally to display current versions and get suggestions
 # for the next version number before running this workflow.
+#
+# Due to security restrictions, when PR is opened the workflows are not triggered automatically.
+# To trigger the workflows, you can make an empty commit with the following command:
+# ```git commit --allow-empty -m "chore: empty commit for triggering workflows" && git push```
 name: Version Management
 
 on: