-
Notifications
You must be signed in to change notification settings - Fork 404
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.
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
refactor: Migrated Next.js instrumentation into agent #2409
Merged
bizob2828
merged 284 commits into
newrelic:next
from
bizob2828:merge-nextjs-instrumentation
Jul 31, 2024
Merged
refactor: Migrated Next.js instrumentation into agent #2409
bizob2828
merged 284 commits into
newrelic:next
from
bizob2828:merge-nextjs-instrumentation
Jul 31, 2024
Conversation
This file contains 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
…e, moved versioned tests for middleware to align with existing structure
Track and record Next.js middleware
…s and very hard to unit test this now that the symbol has been removed
refactored segment tests to use t.segments
added placeholder CHANGELOG, and workflows to prepare and create release
README update
added our standard copy to CONTRIBUTING.md
changed repolinter workflow to check for community plus rules
…za in package-lock
updated instrumentation to require >=8.8.0 of agent, fixed files stanza in package-lock
Add moar docs
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.5 to 1.15.6. - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.15.5...v1.15.6) --- updated-dependencies: - dependency-name: follow-redirects dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…/follow-redirects-1.15.6 chore(deps-dev): bump follow-redirects from 1.15.5 to 1.15.6
feat: Added a test suite for App Router.
feat: Added a shim to externalize all 3rd party libraries the Node.js agent instruments
Co-authored-by: jsumners-nr <[email protected]> Co-authored-by: James Sumners <[email protected]>
Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
svetlanabrennan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
jsumners-nr
requested changes
Jul 30, 2024
bizob2828
force-pushed
the
merge-nextjs-instrumentation
branch
from
July 30, 2024 20:03
58fa070
to
d0c3b96
Compare
jsumners-nr
approved these changes
Jul 31, 2024
Merged
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.
Description
This did a repo migration and retained all commit history. When we merge this PR we cannot squash and merge.
How to Test
Related Issues
Closes #2127