data.json files not updated to 1.2.0
See original GitHub issueActual Behaviour
The reference data files in this repo and the website itself were not updated to the latest 1.2.0 version, the expected changes were not present as well (#4710 for example is still a problem) so it’s not just a version number problem as before.
@lmccart Was there a problem creating a new release or any idea why data.json
/data.min.json
weren’t updated by the release?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
[BUG] npm update not updating package.json #708 - GitHub
The team has decided that fixing usage of npm update --save was the best way moving forwards it enables saving dependency ranges to...
Read more >How to update each dependency in package.json to the latest ...
The best way I know is to run npm info express version then update each dependency in package.json manually. There must be a...
Read more >package.json - npm Docs
This file contains the dependencies renderized and super-streams which can be installed in a new project by executing npm install awesome-web-framework-1.0.0.
Read more >Session & Settings Data — Mu 1.2.0 documentation
The existing files (session.json, settings.json) are implemented as singletons in the settings module, and settings.json is autosaved. New settings to ...
Read more >RFC 8259: The JavaScript Object Notation (JSON) Data ...
Introduction JavaScript Object Notation (JSON) is a text format for the ... It is not expected that future changes in the Unicode specification...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think this has now been resolved thanks to @outofambit’s work moving to github actions.
Yeah I get you. Would it be easier then if we completely separate the releases of p5.js and p5.js-website? So we basically remove the website related stuff from the release process, meaning the reference and the website download links needs to be separately updated manually.
Another alternative is to move most of the update script to CI and have it run on git tags. Maybe that will be more stable than having to clone the website repo, update files, commit and push, all locally?