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
I would like to propose a change for all non-built-in plugins that they provide an additional field called version in register.js that would get written to the db with other “package” info. These would be semantic version numbers maintained by the plugin owner. It would be visible from the dashboard in the “basic” config section.
This would provide us a quick and easy way to know what version of all the plugins we have running in an environment where we don’t have quick and easy access to the code. I am proposing register.js rather than package.json because it makes it easy to parse that data and add it into the Packages collection at startup
There was also a suggestion that this info be included in a health check plugin. It should probably be available to anything that queries for package info
The text was updated successfully, but these errors were encountered:
I would like to propose a change for all non-built-in plugins that they provide an additional field called
version
inregister.js
that would get written to the db with other “package” info. These would be semantic version numbers maintained by the plugin owner. It would be visible from the dashboard in the “basic” config section.This would provide us a quick and easy way to know what version of all the plugins we have running in an environment where we don’t have quick and easy access to the code. I am proposing
register.js
rather thanpackage.json
because it makes it easy to parse that data and add it into thePackages
collection at startupThere was also a suggestion that this info be included in a health check plugin. It should probably be available to anything that queries for package info
The text was updated successfully, but these errors were encountered: