Automate the generation of compatibility report #2157
Comments
newrelic-node-agent-team
added this to Triage Needed: Unprioritized Features
in Node.js Engineering Board
kmudduluru
moved this from Triage Needed: Unprioritized Features
to To do: Features here are prioritized for this sprint
in Node.js Engineering Board
jsumners-nr
moved this from To do: Features here are prioritized for this sprint
to Triage Needed: Unprioritized Features
in Node.js Engineering Board
|
Internal tracking with the docs team is happening via https://new-relic.atlassian.net/browse/NR-262915 |
jsumners-nr
moved this from Triage Needed: Unprioritized Features
to To do: Features here are prioritized for this sprint (jira for remaining tickets)
in Node.js Engineering Board
jsumners-nr
moved this from To do: Features here are prioritized for this sprint (jira for remaining tickets)
to In progress: Issues being worked on
in Node.js Engineering Board
Node.js Engineering Board
automation
moved this from In progress: Issues being worked on
to Done: Issues recently completed
May 28, 2024
This was referenced May 28, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
On release of the agent it should PR the docs-website with a new compatibility report. The workflow should also allow to run manually at anytime.
Acceptance Criteria
On release of the agent I want the most up to date support versions of a library to show on
docs-website. I also want the ability to generate report and PR docs-website at any time.Additional context
The process lives here. The release should publish as a go package so the agent can install this package and run the script. The workflow should also PR the
docs-websiteThe text was updated successfully, but these errors were encountered: