Update release process to specify updating the renderer in VSCode
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 18.3k
- Forks
- 2k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 28
Description
Whenever we issue a new release of Plotly.js, we should update the corresponding version specified in https://github.com/microsoft/vscode-notebook-renderers/blob/ea1eda7bd67e40b20ef218b0fede7f4ce66efeae/package.json#L179 for VSCode users. We see a handful of users who are running into issues with older versions of Plotly.js in VSCode (https://github.com/plotly/plotly.py/issues/4560, https://github.com/plotly/plotly.py/issues/4549, https://github.com/plotly/plotly.py/issues/4554).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Plotly.js release-process documentation or automation, then compare its instructions with package.json at line 179 in microsoft/vscode-notebook-renderers. Done when the release procedure explicitly requires updating the renderer’s Plotly.js version for each new release and links the relevant VSCode context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, vscode
- Domain
- devtools, documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100