build(deps): bump org.eclipse.jgit:org.eclipse.jgit from 7.2.0.202503040940-r to 7.2.1.202505142326-r in /bom in the maven group across 1 directory#2
Open
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Bumps the maven group with 1 update in the /bom directory: [org.eclipse.jgit:org.eclipse.jgit](https://github.com/eclipse-jgit/jgit). Updates `org.eclipse.jgit:org.eclipse.jgit` from 7.2.0.202503040940-r to 7.2.1.202505142326-r - [Commits](eclipse-jgit/jgit@v7.2.0.202503040940-r...v7.2.1.202505142326-r) --- updated-dependencies: - dependency-name: org.eclipse.jgit:org.eclipse.jgit dependency-version: 7.2.1.202505142326-r dependency-type: direct:production dependency-group: maven ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/maven/bom/maven-5c739024ff
branch
from
93529b1 to
e35a0dc
Compare
nxmatic
force-pushed
the
main
branch
2 times, most recently
from
ef70908 to
bc016fb
Compare
nxmatic
force-pushed
the
main
branch
3 times, most recently
from
f2a1018 to
f086c88
Compare
nxmatic
force-pushed
the
main
branch
2 times, most recently
from
165a306 to
d6b84a3
Compare
nxmatic
added a commit
that referenced
this pull request
May 28, 2026
Replace direct component installation with operator pattern: - Vendor cluster-api-operator v0.27.0 (1.6MB) - ClusterApiOperatorLayer installs operator + declares providers as CRs: - CoreProvider (cluster-api v0.27.0) - InfrastructureProvider (incus v0.8.6) - ControlPlaneProvider (rke2 v0.24.4) - ClusterApiOperatorManifestUnit + ClusterApiDomainRegistrar for linking - Update ComponentVersions: clusterctl → clusterApiOperator Mirrors TektonPipelinesLayer pattern for consistency. Operator manages provider lifecycle declaratively. Phase 1 deliverables #1 + #2 complete. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
nxmatic
force-pushed
the
main
branch
2 times, most recently
from
8c8d4c4 to
3d1cbe6
Compare
nxmatic
added a commit
that referenced
this pull request
Jun 7, 2026
Add the preview-only fault-simulation knob to Pulumi.dev.yaml as a documented, commented template — the operator uncomments policy.preview.simulate.<scenario> to order a fake incident and get its runbook from `pulumi preview` without touching infra (ignored during `pulumi up`). Shipped commented so the default preview/up run clean. Memory: record that a contributable fault-simulator seam (a uniform contract for BDD scenario owners to declare how their scenario fails under simulation) is deferred to checkpoint #2 per rule-of-three — one scenario today would guess the wrong abstraction; operator UX is already adequate via config. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
nxmatic
added a commit
that referenced
this pull request
Jun 7, 2026
… @NestedSteps The second checkpoint, modeled DSL-first so it renders offline before the live verifier is wired — proving the runbook+doctor pattern scales beyond one scenario. - ClusterReadinessPhase (kubeconfig / API / controllers) as BDD steps, each driven by an injectable ClusterReadinessProbe returning a Dossier — so a phase shares the doctor's Symptom vocabulary and an ordered incident can target one phase (SimulatedClusterReadinessProbe.failingAt(phase, symptom)). - The systemd-adapter dependency is expressed via @NestedSteps: WhenClusterReadiness injects the systemd-adapter Given/When/Then with @ScenarioStage and replays them as nested sub-steps. The DAG edge becomes a nested scenario — the cert-manager "follow the chain" walk made real — and reuses the same Dossier/Symptom/Generalist machinery as checkpoint #1. - NestedRunbookTest: the cluster scenario renders with the systemd-adapter dependency nested; an ordered fake incident on the api-ready phase yields a targeted FAILED runbook and the doctor diagnoses the phase's symptom. Learned along the way: a Stage's captured-state must not be read back through a public getter — JGiven intercepts public stage methods as steps and corrupts the model flush. The production checkpoint captures the failing dossier via the probe-holder seam, as SystemdAdapterStage already does. Deliberate follow-on (scoped separately): wire the real ClusterBootstrapReadinessVerifier behind a production ClusterReadinessProbe, and build the shared report-node model that lets the plan render into each node's Diagnosis/Mitigation sections (vs. today's inline log) + records dependsOn DAG edges — the two deferrals from A and B converge there now that checkpoint #2 exists. 41/41 seed-master tests pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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 the maven group with 1 update in the /bom directory: org.eclipse.jgit:org.eclipse.jgit.
Updates
org.eclipse.jgit:org.eclipse.jgitfrom 7.2.0.202503040940-r to 7.2.1.202505142326-rCommits
c212cedJGit v7.2.1.202505142326-rc6fc360AmazonS3: Do not accept DOCTYPE and entitiesdab4f52ManifestParser: Do not accept DOCTYPE and entities46a6378Fix package name of spring boot JarLauncher class in jgit.sh79736e4Prepare 7.2.1-SNAPSHOT buildsYou can trigger a rebase of this PR 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.