Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
First official release compatible with Drupal 6 core (note that the alpha1 and alpha2 releases were tagged months ago but never officially released -- they were used internally for initial deployment on drupal.org).
Development snapshot for Drupal 5. Please note that this module will most likely be at EOL sometime before any 6.x releases. The successor will be the VersionControl API.
This release fixes a security vulnerability, all users of cvs.module (4.7.x-1.0 or 4.7.0 from before the new release system) are urged to upgrade. For more details, see DRUPAL-SA-2006-028.
This release includes a new database update: cvs_update_5() which removes a stale entry from the {variable} table. After you upgrade, you should run update.php for your site.
Other changes since cvslog 4.7.x-2.0:
#94000 by dww: adding $Name$ tags for automated version identification.
#97031 by Zen: CVS application form fixes + move all strings to the settings page.
#97128 by dww: don't make the body field required when project administrators edit project releases.
This release fixes a security vulnerability, all users of cvs.module (4.7.x-1.0 or 4.7.0 from before the new release system) are urged to upgrade. For more details, see DRUPAL-SA-2006-028.
This release includes a new database update: cvs_update_5() which removes a stale entry from the {variable} table. After you upgrade, you should run update.php for your site.
The initial stable release compatible with Drupal core 4.7.x. This is the code from before the new release system. It is incompatible with the 4.7.x-2.x series of the project.module, so be sure you use the 4.7.x-1.x series of both modules.
The initial release of the 4.7.x-2.x series which implements the new release system. This series requires a version of the project.module that is also version 4.7.x-2.x, since the project API changed for major revision 2.