Skip to content

Bump docker/build-push-action from 6 to 7#1

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/docker/build-push-action-7
Closed

Bump docker/build-push-action from 6 to 7#1
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/docker/build-push-action-7

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 24, 2026

Bumps docker/build-push-action from 6 to 7.

Release notes

Sourced from docker/build-push-action's releases.

v7.0.0

Full Changelog: docker/build-push-action@v6.19.2...v7.0.0

v6.19.2

Full Changelog: docker/build-push-action@v6.19.1...v6.19.2

v6.19.1

Full Changelog: docker/build-push-action@v6.19.0...v6.19.1

v6.19.0

Full Changelog: docker/build-push-action@v6.18.0...v6.19.0

v6.18.0

[!NOTE] Build summary is now supported with Docker Build Cloud.

Full Changelog: docker/build-push-action@v6.17.0...v6.18.0

v6.17.0

[!NOTE] Build record is now exported using the buildx history export command instead of the legacy export-build tool.

Full Changelog: docker/build-push-action@v6.16.0...v6.17.0

v6.16.0

... (truncated)

Commits
  • f9f3042 Merge pull request #1517 from docker/dependabot/npm_and_yarn/docker/actions-t...
  • 812d5fd chore: update generated content
  • b6f6693 chore(deps): Bump @​docker/actions-toolkit from 0.87.0 to 0.90.0
  • c1c626e Merge pull request #1525 from docker/dependabot/npm_and_yarn/actions/core-3.0.1
  • 51bb284 chore: update generated content
  • 5f7884d chore(deps): Bump @​actions/core from 3.0.0 to 3.0.1
  • e01deff Merge pull request #1521 from docker/dependabot/npm_and_yarn/fast-xml-parser-...
  • 3804d49 chore: update generated content
  • 71e8947 chore(deps): Bump fast-xml-parser from 5.5.7 to 5.8.0
  • 4925ad2 Merge pull request #1526 from docker/dependabot/npm_and_yarn/postcss-8.5.10
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 6 to 7.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](docker/build-push-action@v6...v7)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 24, 2026

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@Musiker15 Musiker15 closed this May 24, 2026
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 24, 2026

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot Bot deleted the dependabot/github_actions/docker/build-push-action-7 branch May 24, 2026 14:46
Musiker15 added a commit that referenced this pull request May 25, 2026
Phase-5 deferred item #1: Milestones. Backend lands first as a clean,
reviewable slice; the UI integration (selector in card-drawer +
management modal) ships as a follow-up PR so reviewers can focus on
the data shape here in isolation.

Schema (prisma/schema.prisma):
- New `Milestone` model: id, boardId, enc_name (encrypted title +
  optional description in one envelope), startAt / endAt (server-visible
  date window — needed for chart range + filtering), archived flag.
  `@@index([boardId, archived])` + `@@index([endAt])` for the typical
  list-by-board and "upcoming deadlines" queries.
- `Card.milestoneId String?` with `Card.milestone Milestone? @relation(...,
  onDelete: SetNull)` so deleting a milestone keeps the cards.
- `@@index([milestoneId])` on Card so per-milestone listing is cheap.

Migration (20260525000001_milestones/migration.sql):
- Hand-written (consistent with the Phase-1 pattern of using
  `prisma migrate diff` only when the shadow DB is reachable). Mirror
  exactly what Prisma generates: CREATE TABLE + ALTER TABLE + indices +
  FKs.

Repository (src/lib/repositories/milestones.ts):
- listForBoard (with includeArchived flag)
- create / update / remove with the existing requireBoardRead /
  requireBoardWrite RBAC guards
- assignCard — board-scoped assignment, validates the milestone lives
  on the same board as the card

API routes:
- GET / POST  /api/boards/[id]/milestones    (list + create)
- PATCH / DELETE  /api/milestones/[id]       (update + delete)
- PUT  /api/cards/[id]/milestone             (assign / unassign)

The encryption shape stays consistent with the rest of the system:
`enc_name` is opaque to the server, dates are server-visible (they
have to be for the burn-down chart range + timeline filtering).

CLAUDE.md updated:
- §7 schema gets the new `Milestone` model + Card.milestoneId
- §8 API endpoints table gets the four new routes
- Phase-7 burn-down can now be implemented (was blocked on "needs
  Milestones")

Follow-up tracked: UI integration (selector in card-drawer + Milestone
management modal). Coming as PR 1b once the backend is in.

Signed-off-by: Musiker15 <info@musiker15.de>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant