You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the security agent team issues a new release the submit a pull request (PR) to use to bump the version, e.g. #2080. However, our continuous integration (CI) setup only runs the standard tests suites, which do not enable the security agent, for all PRs. So it is possible for us to see breakages when the nightly tests run that do enable the security agent, e.g. #2087
Acceptance Criteria
Update the CI configuration to enable the security agent when the PR contains a change to the security agent dependency version such that CI enables the security agent for the runs against the PR
Description
When the security agent team issues a new release the submit a pull request (PR) to use to bump the version, e.g. #2080. However, our continuous integration (CI) setup only runs the standard tests suites, which do not enable the security agent, for all PRs. So it is possible for us to see breakages when the nightly tests run that do enable the security agent, e.g. #2087
Acceptance Criteria
Change the security agent dependency to a pinned version instead of a semver qualifier range of(solved in chore(deps): pin @newrelic/security-agent to 1.0.1 #2089)^
The text was updated successfully, but these errors were encountered: