NO-ISSUE Merged from release/0.1 (#52 )

Reviewed-on: #52
Merge branch 'main' of git.squidspirit.com:squid/blog into release/0.1
2025-02-01 13:34:52 +08:00 · 2025-02-01 13:32:08 +08:00 · 2025-01-28 13:30:27 +08:00 · 2025-01-28 13:23:46 +08:00
2 changed files with 3 additions and 2 deletions
--- a/.gitea/workflows/deployment.yaml
+++ b/.gitea/workflows/deployment.yaml
@ -17,7 +17,7 @@ jobs:
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3
-      - name: Build image and push to registry
+      - name: Login to registry
        uses: docker/login-action@v3
        with:
          registry: ${{ vars.REGISTRY }}
@ -28,6 +28,7 @@ jobs:
        uses: docker/build-push-action@v6
        with:
          push: true
          provenance: false
          context: ./frontend
          tags: |
            ${{ vars.REGISTRY }}/${{ vars.IMAGE_REPO_FRONTEND }}:latest
--- a/frontend/package.json
+++ b/frontend/package.json
@ -1,6 +1,6 @@
 {
  "name": "squidspirit-blog",
-  "version": "0.1.0",
+  "version": "0.1.1",
  "private": true,
  "license": "MIT",
  "scripts": {
Author	SHA1	Message	Date
squid	8d33f2bae3	NO-ISSUE Merged from release/0.1 (#52 ) All checks were successful Frontend CI / build (push) Successful in 1m29s Details Reviewed-on: #52	2025-02-01 13:34:52 +08:00
SquidSpirit	0e022012fe	Merge branch 'main' of git.squidspirit.com:squid/blog into release/0.1 All checks were successful PR Title Check / pr-title-check (pull_request) Successful in 13s Details Frontend CI / build (push) Successful in 1m25s Details	2025-02-01 13:32:08 +08:00
SquidSpirit	93f1bee0ae	NO-ISSUE Upgrade version to 0.1.1 (#42 ) All checks were successful Frontend CI / build (push) Successful in 1m26s Details Deployment / frontend-deployment (release) Successful in 2m3s Details PR Title Check / pr-title-check (pull_request) Successful in 13s Details ### Description As the title. ### Package Changes _No response_ ### Screenshots _No response_ ### Reference _No issue_ ### Checklist - [x] A milestone is set - [ ] The related issuse has been linked to this branch Reviewed-on: #42 Reviewed-by: zoe <zoe@noreply.localhost> Co-authored-by: SquidSpirit <squid@squidspirit.com> Co-committed-by: SquidSpirit <squid@squidspirit.com>	2025-01-28 13:30:27 +08:00
SquidSpirit	f8cf40a3dc	BLOG-36 Fix workflow buildx failed to push (#38 ) All checks were successful Frontend CI / build (push) Successful in 1m34s Details ### Description - As the title. ### Package Changes _No response_ ### Screenshots _No response_ ### Reference - Resolves #36 - Solution: https://stackoverflow.com/questions/75131872/error-failed-to-solve-failed-commit-on-ref-unexpected-status-400-bad-reques - Docker document: https://docs.docker.com/build/ci/github-actions/attestations/#max-level-provenance > Note that adding attestations to an image means you must push the image to a registry directly, as opposed to loading the image to the local image store of the runner. This is because the local image store doesn't support loading images with attestations. ### Checklist - [x] A milestone is set - [x] The related issuse has been linked to this branch Reviewed-on: #38 Reviewed-by: zoe <zoe@noreply.localhost> Co-authored-by: SquidSpirit <squid@squidspirit.com> Co-committed-by: SquidSpirit <squid@squidspirit.com>	2025-01-28 13:23:46 +08:00