Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update dependency pepr to v0.42.0 #190

Merged
merged 1 commit into from
Dec 12, 2024
Merged

fix(deps): update dependency pepr to v0.42.0 #190

merged 1 commit into from
Dec 12, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 7, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pepr 0.38.3 -> 0.42.0 age adoption passing confidence
pepr ^0.38.3 -> ^0.42.0 age adoption passing confidence

Release Notes

defenseunicorns/pepr (pepr)

v0.42.0

Compare Source

Note 🧾

This sprint, the Pepr team focused on enhancing our typing system to improve consistency and address edge cases where types were less robust. We also made significant improvements to our network posture through the KFC, which may impact end users who are strongly typing fetch configurations. These changes extend to all interactions with the Kubernetes API server through CRUD operations that Pepr uses to communicate with the kube-apiserver. While this release has been thoroughly tested and soak, we recommend proceeding with caution, as progress sometimes introduces unforeseen challenges. Check the slack announcement to see metrics related to this release.

oversight, accidentally released 0.42.0 and skipped 0.41.0 - next releases will be pair programmed to avoid this.

Breaking Changes ⚠️

Pepr's fetch is powered by Undici. If you are using a specific RequestInit options on the fetch, you need to migrate to Undici's RequestInit (It is very similar). This probably won't affect you if you are not strongly typing your RequestInit example in journey/pepr-dev.ts.

Here is an example:

let { fetch } = require("pepr");
const { Agent } = require("undici");

const postOpts = {
  method: "POST",
  body: JSON.stringify({
    query: "query { joke {id joke permalink } }",
  }),
  headers: {
    "Content-Type": "application/json; charset=UTF-8",
  },
  dispatcher: new Agent({
    connect: {
      rejectUnauthorized: false,
    },
  }),
};
(async () => {
  let { data, ok } = await fetch(
    "https://icanhazdadjoke.com/graphql",
    postOpts,
  );
  if (ok) {
    console.log(data.data.joke.joke);
  } else {
    console.log("Failed to fetch joke");
  }
})();

This strengthens Pepr's ability to communicate with the Kubernetes Control Plane and reduces transmit bandwidth.

Feat ⛰️

What's Changed ♻️

Full Changelog: defenseunicorns/pepr@v0.40.1...v0.42.0

v0.40.1

Compare Source

A brand new high-severity CVE around cross-spawn hit during the release. This release mitigates the CVE.

What's Changed

Full Changelog: defenseunicorns/pepr@v0.40.0...v0.40.1

v0.40.0

Compare Source

Features

Performance/Stress Testing 🤓
This release we introduce tooling that is allows us to send thousands of request/sec into Pepr's Reconcile action to add visibility into Pepr behavior under heavy load. We are able to control the amount of time that we are dumping in these objects for more stress style scenarios. More information will be coming out on how to run this test yourself at a future date. For now it runs nightly in CI.

> npx ts-node hack/load.cli.ts --help
Usage: load [options] [command]

Load test a Pepr controller and graph/report on resource usage.

Options:
  -V, --version                          output the version number
  -h, --help                             display help for command

Commands:
  prep <src>                             Create testable artifacts
  cluster                                test cluster controls
  deploy [options] <tgz> <img> <module>  deploy a Pepr module for testing
  run [options] <module> <manifest>      run a load test
  post [options]                         post-process load test log
  graph [options]                        generate a graph of load test results
  help [command]                         display help for command

Legacy Watch is removed ⚠️
After ongoing testing and consistently seeing major improvements in our Undici Watch, we have removed the legacy watch option to provide a better performance out of the box and to avoid maintaining two separate watches.

What's Changed
New Contributors

Full Changelog: defenseunicorns/pepr@v0.39.1...v0.40.0

v0.39.1

Compare Source

What's Changed

Full Changelog: defenseunicorns/pepr@v0.39.0...v0.39.1

v0.39.0

Compare Source

Features
What's Changed
Dependabot
New Contributors

Full Changelog: defenseunicorns/pepr@v0.38.3...v0.39.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/pepr-0.x branch from 075d489 to 59cae08 Compare November 12, 2024 20:59
@renovate renovate bot changed the title Update dependency pepr to v0.39.0 Update dependency pepr to v0.39.1 Nov 12, 2024
@renovate renovate bot force-pushed the renovate/pepr-0.x branch from 59cae08 to 7048a60 Compare November 14, 2024 21:11
@renovate renovate bot changed the title Update dependency pepr to v0.39.1 fix(deps): update dependency pepr to v0.39.1 Nov 14, 2024
@renovate renovate bot force-pushed the renovate/pepr-0.x branch 2 times, most recently from 2fd87f0 to a9a4dc4 Compare November 20, 2024 16:29
@renovate renovate bot changed the title fix(deps): update dependency pepr to v0.39.1 fix(deps): update dependency pepr to v0.40.0 Nov 20, 2024
@renovate renovate bot force-pushed the renovate/pepr-0.x branch from a9a4dc4 to 42a758d Compare November 20, 2024 20:49
@renovate renovate bot changed the title fix(deps): update dependency pepr to v0.40.0 fix(deps): update dependency pepr to v0.40.1 Nov 20, 2024
@renovate renovate bot force-pushed the renovate/pepr-0.x branch from 42a758d to 4e8311a Compare December 6, 2024 16:17
@renovate renovate bot changed the title fix(deps): update dependency pepr to v0.40.1 fix(deps): update dependency pepr to v0.42.0 Dec 6, 2024
@samayer12 samayer12 merged commit d2406f3 into main Dec 12, 2024
2 checks passed
@samayer12 samayer12 deleted the renovate/pepr-0.x branch December 12, 2024 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@samayer12