chore(deps): bump docker/metadata-action from 5.10.0 to 6.1.0#4
Closed
dependabot[bot] wants to merge 20 commits into
Closed
chore(deps): bump docker/metadata-action from 5.10.0 to 6.1.0#4dependabot[bot] wants to merge 20 commits into
dependabot[bot] wants to merge 20 commits into
Conversation
First public alpha. Wire-protocol proxy (TLS termination, gzip, session rotation, fail-open passthrough), literal-safe semantic cache with blame mode, in-flight coalescing, deterministic rewrite pack, predictive auto-suspend with enforce mode, cost attribution, realized-savings ledger with signed Ed25519 evidence bundles, replay simulator, and a release pipeline ported from osodevops/kafka-backup (cargo-dist, release tagger, version guard, semver checks). 98 tests; integration-verified against the official snowflake-connector-python via fakesnow. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Not needed for any current distribution channel (binaries, installers, Homebrew, Scoop, Docker) and was blocking releases on token scopes. Reinstate when a published crate needs to depend on chukei-core. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
RELEASE_PAT (fine-grained org PAT) returned 404 on the releases API — the repo isn't in its grant. The workflow already has contents: write and nothing triggers on release events, so the built-in token suffices. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ng, pilot kit - fix: rustls CryptoProvider was only installed in the serve path, so 'chukei doctor' panicked on TLS configs (shipped in v0.1.0). Now chukei_core::init_crypto() runs at CLI start; reproducer test in its own test binary. - harden: cache dir 0700, cache entries + savings ledger 0600 (query results/metadata at rest), with unit tests. - live pilot harness: scripts/live-pilot.sh + scripts/live_matrix.py — TLS mode (local CA, venv-scoped trust), auth modes password/keypair/PAT, stages core/shapes/concurrency, trace-level credential-leak audit. All validated against a real Snowflake account. - customer kit: config/customer-pilot.yaml (conservative profile, validate-clean), docs/deployment.md, deploy/docker-compose.yaml, deploy/k8s.yaml. - version 0.1.0 → 0.2.0 (minor: new chukei-core public API init_crypto). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
scripts/soak.sh / soak_traffic.py / soak-report.sh: overnight mixed-traffic soak with RSS sampling and a morning go/no-go gate. deployment.md now states measured outage behavior: sub-retry-budget restarts are invisible, sessions resume without re-login. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
seo-research skill output: Perplexity discovery (market, competitor content, LLM visibility), 717-keyword SEMrush masterlist with LLM-weighted scoring, semantic topical map + ~88-page Docusaurus site structure (mirrors kafka-backup-docs), 8 generation-ready content briefs, llms.txt template, 6-week editorial calendar, Reddit distribution plan. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
….2, not day 1) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The login handler stored user + application but defaulted warehouse to None, so on real driver traffic the suspend model never observed a single arrival — suggest and enforce modes were both blind. Found when the live enforce drill produced zero recommendations despite warmed traffic; the older enforce e2e test seeded the model directly and masked the gap. - Login: warehouse from response sessionInfo.warehouseName, fallback to the ?warehouse= login query param. - USE WAREHOUSE statements re-point the session's warehouse mid-stream. - Full-wire-path regression test (login → query → model observes WH, USE WAREHOUSE switching) in proxy_e2e. - Plus this session's earlier suspend fixes: arrivals recorded post-result (cache hits and metadata statements no longer reset the idle model), model gates (min_observations/horizon_secs/p_threshold) configurable. 105 tests green. v0.2.1. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ault 300) The 5-minute constant masked enforce-mode validation: the sweeper fires ~10s after the min_observations-th arrival (correct), the next query auto-resumes the warehouse, and the cooldown then blocks re-suspends for longer than any reasonable observation window. Proven via Snowflake's queued_provisioning_time: arrival 5 spent 93ms resuming the warehouse chukei had suspended 85s earlier. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…e truth Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…hitecture README hero + status (now pilot-ready with validation receipts), Cargo description, GitHub repo description, llms.txt template. Per seo-research/output/positioning.md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Hero+badges, features, full installation matrix, replay try-it, quickstart, competitor comparison table, when-NOT-to-use, docs table, CLI reference, production-validation receipts, enterprise tier, acknowledgments. Repo description + topics updated to match. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…dist host) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 5.10.0 to 6.1.0. - [Release notes](https://github.com/docker/metadata-action/releases) - [Commits](docker/metadata-action@c299e40...80c7e94) --- updated-dependencies: - dependency-name: docker/metadata-action dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
Author
|
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 If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/github_actions/docker/metadata-action-6.1.0
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps docker/metadata-action from 5.10.0 to 6.1.0.
Release notes
Sourced from docker/metadata-action's releases.
Commits
80c7e94Merge pull request #613 from docker/dependabot/npm_and_yarn/docker/actions-to...8e0ddabchore: update generated contenta8db14bchore(deps): Bump@docker/actions-toolkitfrom 0.79.0 to 0.90.063a7371Merge pull request #617 from docker/dependabot/npm_and_yarn/csv-parse-6.2.0c6916a6chore: update generated contentaca9205chore(deps): Bump csv-parse from 6.1.0 to 6.2.19dcfe60Merge pull request #629 from docker/dependabot/npm_and_yarn/handlebars-4.7.943dea76chore: update generated content7a56f5achore(deps): Bump handlebars from 4.7.8 to 4.7.9e49e0aaMerge pull request #658 from docker/dependabot/npm_and_yarn/brace-expansion-5...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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)