fix(ci): restore --no-restore drop + build-number offset to keep continuity

- Dockerfile: drop --no-restore on dotnet publish. BuildKit cache mounts only exist for the duration of a single RUN, so the cache from the prior 'dotnet restore' is gone when 'publish' starts; passing --no-restore made publish fail with NETSDK1064 (package not found). Re-mounting the cache keeps the second restore essentially free.

- main.yml + feature.yml: add +247 offset to github.run_number so numbering continues from the previous git-count value (~252) instead of restarting at 1.

Fixes failing main.yml run #5.

Author: alfarahn

.github/workflows/feature.yml

@@ -60,7 +60,10 @@ jobs:
           echo "branch=$BRANCH" >> $GITHUB_OUTPUT
           echo "tag_branch=$TAG_BRANCH" >> $GITHUB_OUTPUT
           echo "sha=${GITHUB_SHA::7}" >> $GITHUB_OUTPUT
-          echo "build=${{ github.run_number }}" >> $GITHUB_OUTPUT
+          # Offset so we keep numbering continuous after switching from
+          # `git rev-list --count HEAD` (which had reached 252) to run_number
+          # (which restarted at 1 when the workflow file was renamed).
+          echo "build=$(( ${{ github.run_number }} + 247 ))" >> $GITHUB_OUTPUT
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v4

.github/workflows/main.yml

@@ -47,7 +47,10 @@ jobs:
         id: meta
         run: |
           echo "sha=${GITHUB_SHA::7}" >> $GITHUB_OUTPUT
-          echo "build=${{ github.run_number }}" >> $GITHUB_OUTPUT
+          # Offset so we keep numbering continuous after switching from
+          # `git rev-list --count HEAD` (which had reached 252) to run_number
+          # (which restarted at 1 when the workflow file was renamed).
+          echo "build=$(( ${{ github.run_number }} + 247 ))" >> $GITHUB_OUTPUT
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v4

src/Dashboard/Dockerfile

@@ -20,8 +20,12 @@ RUN --mount=type=cache,target=/root/.nuget/packages \
     dotnet restore -r linux-x64
 COPY . .
 COPY --from=frontend /app/wwwroot ./wwwroot/
+# Note: we deliberately do NOT pass --no-restore here. BuildKit cache mounts
+# only exist for the duration of a single RUN, so the restore step above
+# can't share its /root/.nuget/packages with this step. Re-mounting the
+# cache makes the second restore essentially free (everything cache-hits).
 RUN --mount=type=cache,target=/root/.nuget/packages \
-    dotnet publish -c Release -r linux-x64 --self-contained false --no-restore -o /app/publish
+    dotnet publish -c Release -r linux-x64 --self-contained false -o /app/publish
 
 # ── Stage 3: Final runtime image ──
 FROM mcr.microsoft.com/dotnet/aspnet:10.0 AS final