repos/webexmemebot
4
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Releases 47 Activity
525 Commits 1 Branch 47 Tags
4c51e697d9f58de2da730867acfe2ec396a5df87
Commit Graph

87 Commits

Author SHA1 Message Date
Luke Tainton
4c51e697d9 Update .gitea/workflows/ci.yml
Some checks failed
Security / sonarqube (push) Failing after 31s
Details
Security / snyk (push) Successful in 1m0s
Details
2025-06-06 19:15:51 +02:00
Luke Tainton
b8918b3d03 Update .gitea/workflows/release.yml
Some checks failed
Release / Tag release (push) Successful in 28s
Details
Release / Create Release (push) Successful in 13s
Details
Release / Publish Docker Images (push) Failing after 2m7s
Details
Security / sonarqube (push) Failing after 2m8s
Details
Security / snyk (push) Successful in 1m32s
Details
2025-05-10 22:27:22 +02:00
Luke Tainton
4369470727 chore(ci): remove get_release_id task (#484)
All checks were successful
Security / snyk (push) Successful in 2m54s
Details
Security / sonarqube (push) Successful in 3m22s
Details 
Okay, I will analyze the provided Git diff and explain the proposed changes.

**Overall Summary**

The diff shows a commented-out job in the `.gitea/workflows/release.yml` file.  The job `get_release_id` and its associated steps are being commented out. Also, the `needs` attribute for `create_docker` job has been changed.

**Detailed Explanation**

1.  **Commenting out the `get_release_id` job:**

    The entire `get_release_id` job block is being commented out. This includes the `name`, `runs-on`, `needs`, `outputs`, and `steps` sections.

    ```diff
    --- a/.gitea/workflows/release.yml
    +++ b/.gitea/workflows/release.yml
    @@ -23,26 +23,26 @@ jobs:
        secrets:
          ACTIONS_TOKEN: ${{ secrets.ACTIONS_TOKEN }}

    -  get_release_id:
    -    name: Get Release ID
    -    runs-on: ubuntu-latest
    -    needs: [tag, create_release]
    -    outputs:
    -      releaseid: ${{ steps.getid.outputs.releaseid }}
    -    steps:
    -      - name: Get Release ID
    -        id: getid
    -        run: |
    -          rid=$(curl -s -X 'GET' \
    -          -H 'accept: application/json' \
    -          '${{ gitea.server_url }}/api/v1/repos/${{ gitea.repository }}/releases/latest' | jq -r '.id')
    -          echo "releaseid=$rid" >> "$GITEA_OUTPUT"
    -          echo "$rid"
    +  # get_release_id:
    +  #   name: Get Release ID
    +  #   runs-on: ubuntu-latest
    +  #   needs: create_release
    +  #   outputs:
    +  #     releaseid: ${{ steps.getid.outputs.releaseid }}
    +  #   steps:
    +  #     - name: Get Release ID
    +  #     - id: getid
    +  #     - run: |
    +  #       rid=$(curl -s -X 'GET' \
    +  #       -H 'accept: application/json' \
    +  #       '${{ gitea.server_url }}/api/v1/repos/${{ gitea.repository }}/releases/latest' | jq -r '.id')
    +  #       echo "releaseid=$rid" >> "$GITEA_OUTPUT"
    +  #       echo "$rid"
    ```

    The original `get_release_id` job was responsible for fetching the ID of the latest release using a `curl` command against the Gitea API. The output `releaseid` was likely intended to be used by subsequent jobs.  Commenting this out means this ID will no longer be available.

2.  **Modifying the `needs` attribute for the `create_docker` job:**

    The `needs` attribute of the `create_docker` job has been modified.

    ```diff
    --- a/.gitea/workflows/release.yml
    +++ b/.gitea/workflows/release.yml
    @@ -50,7 +50,7 @@
     create_docker:
       name: Publish Docker Images
       runs-on: ubuntu-latest
    -  needs: tag
    +  needs: create_release
       steps:
         - name: Update Docker configuration
           continue-on-error: true
    ```

    The original `needs: tag` has been changed to `needs: create_release`. This means that the `create_docker` job will now only run after the `create_release` job has completed successfully, instead of after the `tag` job.

**Impact and Potential Reasons**

*   **Removal of Release ID:** By commenting out `get_release_id`, any downstream jobs relying on the `releaseid` output will likely break.  The reason for removing this is not apparent from the diff, but it could be due to:

    *   The ID is no longer needed.
    *   The method for obtaining the ID has changed and is implemented elsewhere.
    *   The job was causing issues and is being temporarily disabled.
    *   The job was not functioning as intended.

*   **Changing Dependency for Docker Image Creation:**  Changing the dependency of `create_docker` to `create_release` suggests a change in the intended workflow.  Previously, the Docker image creation was triggered by the creation of a tag. Now, it's triggered specifically by the creation of a release. This might be done to ensure that Docker images are only built and published when a formal release is made, rather than on every tag.

It's important to examine the broader context of the pull request and any associated issues to understand the rationale behind these changes more fully.

Reviewed-on: #484
 2025-05-10 22:15:19 +02:00
Luke Tainton
ed35c1b8e6 fix(ci): fix release workflow (#482)
Some checks failed
Security / snyk (push) Has been cancelled
Details
Security / sonarqube (push) Has been cancelled
Details 
Reviewed-on: #482
 2025-05-10 21:39:56 +02:00
Renovate [BOT]
0aecbae7d6 chore(deps): update sonarsource/sonarqube-scan-action action to v5.2.0 (#480)
All checks were successful
Security / sonarqube (push) Successful in 10m54s
Details
Security / snyk (push) Successful in 13m44s
Details 
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [SonarSource/sonarqube-scan-action](https://github.com/SonarSource/sonarqube-scan-action) | action | minor | `v5.1.0` -> `v5.2.0` |

---

### Release Notes

<details>
<summary>SonarSource/sonarqube-scan-action (SonarSource/sonarqube-scan-action)</summary>

### [`v5.2.0`](https://github.com/SonarSource/sonarqube-scan-action/releases/tag/v5.2.0)

[Compare Source](https://github.com/SonarSource/sonarqube-scan-action/compare/v5.1.0...v5.2.0)

##### What's Changed

-   SQSCANGHA-90 remove mend dead conf by [@&#8203;pierre-guillot-gh](https://github.com/pierre-guillot-gh) in https://github.com/SonarSource/sonarqube-scan-action/pull/184
-   SQSCANGHA-89 Attempt to fix command injection by [@&#8203;henryju](https://github.com/henryju) in https://github.com/SonarSource/sonarqube-scan-action/pull/186
-   SQSCANGHA-93 Fix madhead/semver-utils' version by [@&#8203;csaba-feher-sonarsource](https://github.com/csaba-feher-sonarsource) in https://github.com/SonarSource/sonarqube-scan-action/pull/187
-   SQSCANGHA-94 Update version update logic by [@&#8203;csaba-feher-sonarsource](https://github.com/csaba-feher-sonarsource) in https://github.com/SonarSource/sonarqube-scan-action/pull/188
-   SQSCANGHA-92 Validate scanner version by [@&#8203;csaba-feher-sonarsource](https://github.com/csaba-feher-sonarsource) in https://github.com/SonarSource/sonarqube-scan-action/pull/189

**Full Changelog**: https://github.com/SonarSource/sonarqube-scan-action/compare/v5...v5.2.0

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC43LjAiLCJ1cGRhdGVkSW5WZXIiOiI0MC43LjAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbInR5cGUvZGVwZW5kZW5jaWVzIl19-->

Reviewed-on: #480
Co-authored-by: Renovate [BOT] <renovate-bot@git.tainton.uk>
Co-committed-by: Renovate [BOT] <renovate-bot@git.tainton.uk>
 2025-05-07 20:49:55 +02:00
Renovate [BOT]
e54838e6ac chore(deps): update sonarsource/sonarqube-scan-action action to v5.1.0 (#476)
Some checks failed
Release / Manual Trigger Cleanup (push) Has been skipped
Details
Release / Create Release (push) Successful in 19s
Details
Release / Build Docker Images (push) Failing after 1m57s
Details
Security / sonarqube (push) Successful in 2m5s
Details
Security / snyk (push) Successful in 3m14s
Details 
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [SonarSource/sonarqube-scan-action](https://github.com/SonarSource/sonarqube-scan-action) | action | minor | `v5.0.0` -> `v5.1.0` |

---

### Release Notes

<details>
<summary>SonarSource/sonarqube-scan-action (SonarSource/sonarqube-scan-action)</summary>

### [`v5.1.0`](https://github.com/SonarSource/sonarqube-scan-action/releases/tag/v5.1.0)

[Compare Source](https://github.com/SonarSource/sonarqube-scan-action/compare/v5.0.0...v5.1.0)

##### What's Changed

-   Update SonarScanner CLI to 7.1.0.4889 to support sonar.region=us by [@&#8203;github-actions](https://github.com/github-actions) in https://github.com/SonarSource/sonarqube-scan-action/pull/183

**Full Changelog**: https://github.com/SonarSource/sonarqube-scan-action/compare/v5.0.0...v5.1.0

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMTEuNCIsInVwZGF0ZWRJblZlciI6IjM5LjIxMS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL2RlcGVuZGVuY2llcyJdfQ==-->

Reviewed-on: #476
Co-authored-by: Renovate [BOT] <renovate-bot@git.tainton.uk>
Co-committed-by: Renovate [BOT] <renovate-bot@git.tainton.uk>
 2025-03-24 19:18:27 +01:00
Luke Tainton
6530b4c620 Update .gitea/workflows/release.yml
Some checks failed
Release / Manual Trigger Cleanup (push) Has been skipped
Details
Release / Create Release (push) Successful in 32s
Details
Release / Build Docker Images (push) Failing after 2m49s
Details
Security / sonarqube (push) Successful in 6m44s
Details
Security / snyk (push) Successful in 8m24s
Details
2025-02-18 22:39:49 +01:00
Luke Tainton
74c1bea948 Update .gitea/workflows/release.yml
All checks were successful
Security / sonarqube (push) Successful in 55s
Details
Security / snyk (push) Successful in 57s
Details
2025-02-18 22:37:51 +01:00
Luke Tainton
a5312ba3fb Update .gitea/workflows/release.yml
All checks were successful
Security / sonarqube (push) Successful in 1m3s
Details
Security / snyk (push) Successful in 1m4s
Details
2025-02-18 22:31:04 +01:00
Renovate [BOT]
1122726fc9 chore(deps): update sonarsource/sonarqube-scan-action action to v5 (#470)
All checks were successful
Security / sonarqube (push) Successful in 4m6s
Details
Security / snyk (push) Successful in 4m55s
Details 
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [SonarSource/sonarqube-scan-action](https://github.com/SonarSource/sonarqube-scan-action) | action | major | `v4.2.1` -> `v5.0.0` |

---

### Release Notes

<details>
<summary>SonarSource/sonarqube-scan-action (SonarSource/sonarqube-scan-action)</summary>

### [`v5.0.0`](https://github.com/SonarSource/sonarqube-scan-action/releases/tag/v5.0.0)

[Compare Source](https://github.com/SonarSource/sonarqube-scan-action/compare/v4.2.1...v5.0.0)

#### What's Changed

-   SQSCANGHA-81 Update SonarScanner CLI to 7.0.2.4839 by [@&#8203;github-actions](https://github.com/github-actions) in https://github.com/SonarSource/sonarqube-scan-action/pull/175

**Full Changelog**: https://github.com/SonarSource/sonarqube-scan-action/compare/v4...v5.0.0

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xNzEuMyIsInVwZGF0ZWRJblZlciI6IjM5LjE3MS4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJ0eXBlL2RlcGVuZGVuY2llcyJdfQ==-->

Reviewed-on: #470
Reviewed-by: Luke Tainton <luke@tainton.uk>
Co-authored-by: Renovate [BOT] <renovate-bot@git.tainton.uk>
Co-committed-by: Renovate [BOT] <renovate-bot@git.tainton.uk>
 2025-02-17 12:02:39 +01:00
Luke Tainton
44d6f9d161 feat(ci): fix CI, switch to self-hosted SonarQube
All checks were successful
Enforce Conventional Commit PR Title / Validate PR Title (pull_request_target) Successful in 5s
Details
CI / ci (pull_request) Successful in 1m29s
Details
Security / sonarqube (push) Successful in 3m9s
Details
Security / snyk (push) Successful in 4m25s
Details
2025-02-09 20:38:33 +00:00
Renovate [BOT]
a9895a9807 chore(deps): update https://git.tainton.uk/actions/conventional-commits-check-action action to v1.2.4
Some checks failed
Enforce Conventional Commit PR Title / Validate PR Title (pull_request_target) Failing after 6s
Details
CI / ci (pull_request) Successful in 2m17s
Details
2025-02-09 20:10:40 +00:00
Renovate [BOT]
dea03bb39f chore(deps): update https://git.tainton.uk/actions/conventional-commits-check-action action to v1.2.3
Some checks failed
Enforce Conventional Commit PR Title / Validate PR Title (pull_request_target) Failing after 6s
Details
CI / ci (pull_request) Successful in 1m0s
Details
2025-02-04 20:03:51 +00:00
Luke Tainton
7fa0955d23 fix(ci): switch poetry to uv
All checks were successful
Enforce Conventional Commit PR Title / Validate PR Title (pull_request) Successful in 3s
Details
CI / ci (pull_request) Successful in 2m11s
Details
2025-01-03 16:46:00 +00:00
Luke Tainton
2a5f074002 feat: switch to uv
Some checks failed
Enforce Conventional Commit PR Title / Validate PR Title (pull_request) Successful in 3s
Details
CI / ci (pull_request) Failing after 17s
Details
2025-01-03 16:41:14 +00:00
Luke Tainton
f833c986b9 fix(ci): bump actions/conventional-commits-check-action to v1.1.1 2025-01-02 23:47:10 +01:00
Luke Tainton
9cc478c66d chore(ci): bump actions/conventional-commits-check-action to v1.1.0 2025-01-02 23:43:46 +01:00
Luke Tainton
a5949e1efe fix(ci): correct name of action 2025-01-02 22:36:58 +00:00
Luke Tainton
1086eb3d18 fix(ci): switch to custom action 2025-01-02 22:32:31 +00:00
Renovate [BOT]
2790eb1370 chore(deps): update docker/build-push-action action to v6
Some checks failed
Enforce Conventional Commit PR Title / Validate PR Title (pull_request) Failing after 5s
Details
CI / ci (pull_request) Successful in 1m12s
Details
2025-01-02 21:01:09 +00:00
Luke Tainton
490e961397 fix(ci): switch back to previous module
Some checks failed
Enforce Conventional Commit PR Title / Validate PR Title (pull_request) Failing after 4s
Details
2025-01-02 20:43:17 +00:00
Luke Tainton
bb889af36e fix(ci): switch back to previous module 2025-01-02 20:41:39 +00:00
Luke Tainton
a48d7d9ae5 fix(ci): switch conventional commit PR title module 2025-01-02 20:35:36 +00:00
Luke Tainton
96a836cc17 feat(ci): enforce conventional commit PR titles
All checks were successful
CI / ci (pull_request) Successful in 59s
Details
2025-01-02 20:25:07 +00:00
Luke Tainton
89c1f64386 fix(ci): use the conventionalcommits preset instead of angular 2025-01-02 20:19:37 +00:00
Luke Tainton
f2138ba2b7 fix(ci): build and push correctly 2025-01-02 20:03:38 +00:00
Luke Tainton
b5b3388a98 fix(ci): build and push correctly 2025-01-02 20:01:07 +00:00
Luke Tainton
70e3427b38 fix(ci): build and push correctly 2025-01-02 19:56:29 +00:00
Luke Tainton
d7884e9149 fix(ci): build and push correctly 2025-01-02 19:53:31 +00:00
Luke Tainton
f256e6bd1a fix(ci): build and push correctly 2025-01-02 19:46:54 +00:00
Luke Tainton
9f9f03b521 fix(ci): build and push correctly 2025-01-02 19:37:55 +00:00
Luke Tainton
a4c1ae8222 fix(ci): print metadata 2025-01-02 19:27:55 +00:00
Luke Tainton
4db2dd8ea5 fix(ci): manually build and push images 2025-01-02 19:19:43 +00:00
Luke Tainton
f68b5e29d1 fix(ci): manually build and push images 2025-01-02 19:17:43 +00:00
Luke Tainton
26e51e23b8 fix(ci): manually build and push images 2025-01-02 19:15:50 +00:00
Luke Tainton
523648ab73 fix(ci): manually build and push images 2025-01-02 19:09:47 +00:00
Luke Tainton
abb2b3202c fix(ci): manually build and push images 2025-01-02 19:07:34 +00:00
Luke Tainton
9375ae10c3 fix(ci): manually build and push images 2025-01-02 19:05:19 +00:00
Luke Tainton
fb35156a28 fix(ci): allow insecure registry 2025-01-02 18:47:33 +00:00
Luke Tainton
d3fab75acb fix(ci): correct name of CI to match branch protection rules 2025-01-02 18:43:23 +00:00
Luke Tainton
b69609551f fix(ci): re-enable pushing of images to registry 2025-01-02 18:41:30 +00:00
Luke Tainton
d616711cf5 fix(ci): re-enable pushing of images to registry 2025-01-02 18:38:22 +00:00
Luke Tainton
2a7df3d413 fix(ci): use metadata module to extract tags 2025-01-02 18:32:06 +00:00
Luke Tainton
edff65d35d fix(ci): correct docker push cmds 2025-01-02 18:21:12 +00:00
Luke Tainton
d006ebf9fc fix(ci): correct docker push cmds for Gitea images 2025-01-02 18:17:07 +00:00
Luke Tainton
0389ad841b fix(ci): correctly retrieve release name 2025-01-02 18:14:44 +00:00
Luke Tainton
c946991eb2 fix(ci): correctly retrieve release name 2025-01-02 18:08:16 +00:00
Luke Tainton
e1bc246e10 chore(ci): clean up release workflow 2025-01-02 18:01:56 +00:00
Luke Tainton
14ee2bca3a fix(ci): directly call API to create release fix 2 2025-01-02 17:58:22 +00:00
Luke Tainton
23a28d2226 fix(ci): directly call API to create release fix 2025-01-02 17:54:53 +00:00