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
This could be done by running a sort of CRON job on github actions every month so that cran_monthly_package_number and may be also cran_packages_history are regularly updated.
A function must then be written that will perform the automatic version bump.
The versioning pattern could be the following:
major: functional version only incremented if there is a change in API or added feature.
minor.patch.dev: a date stamp of the form yy.mm.dd corresponding to the date of the automatic update.
ex: 1.22.07.01 This will be version 1 with datasets updated on July 1st 2022.
The text was updated successfully, but these errors were encountered:
ALanguillaume
changed the title
Unable autoversionning via github actions
Enable autoversionning via github actions
Jun 30, 2022
Ideally the datasets should be updated regularly.
This could be done by running a sort of CRON job on github actions every month so that
cran_monthly_package_number
and may be alsocran_packages_history
are regularly updated.A function must then be written that will perform the automatic version bump.
The versioning pattern could be the following:
ex:
1.22.07.01
This will be version 1 with datasets updated on July 1st 2022.The text was updated successfully, but these errors were encountered: