Updates
See which arcy.js version each environment runs against the newest release, and what every newer version changes in your code.
Configure > Updates shows which arcy.js version the environment in the address runs, the newest version, and, for an npm install, what each version in between changes.
Before you start
- ARCY learns an environment's version the first time a page with arcy.js on it loads there. Until then the page says so and links Installation.
- arcy.js 0.2.9 and later also report whether they came from the pasted script or from the npm package. An older install does not, so the page shows both paths.
Setting it up
The status line reads, for example, "Production runs arcy.js 0.2.5, last seen 2h ago. Newest is 0.2.8."
- Pasted the ARCY script: arcy.js updates itself. There is nothing to do, and no cards appear.
- Installed the npm package: one card per newer version, newest first, with its release date, its notes and What your code must change. The update section gives the command for your package manager, and the agent logos copy the update as a task for your coding agent, with every change your code must make on the way.
- Already on the newest: There is nothing to update.
Set up the Update bot goes to Installation: the bot opens a pull request for each new release and merges patch releases once your checks pass.
What it changes
- The page reads the version live. The New arcy.js release alert on Alerts clears up to an hour after the environment reports the new version.
- The notes are the Changelog. A version older than the Changelog has no notes here.