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

chore(deps): update pepr #34

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update pepr #34

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 14, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pepr 0.22.2 -> 0.45.0 age adoption passing confidence
ts-jest (source) 29.1.1 -> 29.2.5 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

defenseunicorns/pepr (pepr)

v0.45.0

Compare Source

Features 🆕

Introducing Nightlies 🌃

Wanna test new CLI or Controller features before they are release? How's how!

> npx pepr@nightly -V
0.44.0-nightly.7

What's Changed ♻️

Dependabot 🤖

Next Release Theme: Testing!

Full Changelog: defenseunicorns/pepr@v0.44.0...v0.45.0

v0.44.0

Compare Source

What's Changed

Full Changelog: defenseunicorns/pepr@v0.43.0...v0.44.0

v0.43.0

Compare Source

Features 🤓

Allows additional ignored namespaces to be set in the helm chart in addition to the namespaces set in pepr section of package.json.

Watch Out 🚧

Rebuild required (npx pepr build) - The distroless image has a smaller footprint with less CVEs, however, it does not have node in the same path on the container. Therefore, we needed to switch the commands on the deployments for args. Make sure you do a rebuild and this will be done for you.

Note- We always recommend rebuilding when you bring in new versions.

What's Changed ♻️

Full Changelog: defenseunicorns/pepr@v0.42.3...v0.43.0

v0.42.3

Compare Source

What's Changed

Full Changelog: defenseunicorns/pepr@v0.42.2...v0.42.3

v0.42.2

Compare Source

What's Changed

Full Changelog: defenseunicorns/pepr@v0.42.1...v0.42.2

v0.42.1

Compare Source

Note 🧾

We realized that when doing a setItemAndWait() or removeItemAndWait() with patch values that were the same as the values already in the Pepr store, an error could occur. This release addresses that error and enhances store code.

What's Changed ♻️

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

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

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • 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 branch 10 times, most recently from b4dbd44 to 0ba276f Compare December 18, 2023 23:06
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from 7be0603 to b35f99a Compare December 23, 2023 05:51
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from 4805fb1 to b14ba60 Compare January 4, 2024 05:37
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from e744931 to 44c3ee8 Compare January 18, 2024 03:01
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from 2fef7ff to e385c35 Compare January 22, 2024 20:42
@github-actions github-actions bot mentioned this pull request Jan 23, 2024
Open
@renovate renovate bot changed the title chore: update pepr chore(deps): update pepr Jan 23, 2024
@renovate renovate bot force-pushed the renovate/pepr branch 3 times, most recently from aa2a877 to 00a1993 Compare January 30, 2024 02:51
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from 0cd9d76 to 51adc31 Compare February 6, 2024 02:46
@renovate renovate bot force-pushed the renovate/pepr branch 3 times, most recently from 6e39cea to b3a8bbd Compare February 23, 2024 05:50
@renovate renovate bot force-pushed the renovate/pepr branch 3 times, most recently from f7acf30 to 70269f3 Compare June 19, 2024 05:52
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from 290f0a8 to 2107501 Compare July 2, 2024 20:33
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from cc0e37e to 49aac4b Compare July 12, 2024 11:49
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from eed0188 to 1928624 Compare July 23, 2024 23:52
@renovate renovate bot force-pushed the renovate/pepr branch from 1928624 to e515633 Compare August 2, 2024 02:37
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from 8f8b9f5 to 8588337 Compare August 15, 2024 20:43
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from b41b2e8 to 8849f36 Compare August 30, 2024 00:00
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from 5191f6a to 4e93683 Compare October 3, 2024 02:34
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from a0227cf to f028312 Compare October 19, 2024 02:34
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from 450490d to 825b439 Compare November 13, 2024 11:58
@renovate renovate bot force-pushed the renovate/pepr branch 2 times, most recently from 2a1a11a to acbed05 Compare January 25, 2025 07:13
@renovate
chore(deps): update pepr
4d18a88 
| datasource | package | from   | to     |
| ---------- | ------- | ------ | ------ |
| npm        | pepr    | 0.22.2 | 0.45.0 |
| npm        | ts-jest | 29.1.1 | 29.2.5 |
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.
0 participants