All Versions
34
Latest Version
Avg Release Cycle
73 days
Latest Release
50 days ago

Changelog History
Page 1

  • v3.11.2

    September 29, 2019

    🍱 🏠 Housekeeping

  • v3.11.1

    August 29, 2019
    • 🚀 #2027: Batch rm -rf calls in deploy:cleanup to fix an error when there are too many old releases @azin634
  • v3.11.0

    June 03, 2018
    • 0️⃣ #1972: fallback ask to default when used in non interactive session
  • v3.10.2

    April 15, 2018

    💥 Breaking changes:

    • None

    🛠 Fixes:

    • 🚚 #1977: Remove append operator when writing the git file - @mmiller1
  • v3.10.1

    December 08, 2017

    💥 Breaking changes:

    • None

    🛠 Fixes:

    • #1954: Fix Host filtering when multi-host strings contain 0
  • v3.10.0

    October 23, 2017

    🚀 As of this release, version 2.x of Capistrano is officially End of Life. No further releases of 2.x series are planned, and pull requests against 2.x are no longer accepted. The maintainers encourage you to upgrade to 3.x if possible.

    💥 Breaking changes:

    • None

    🆕 New features:

    • 🚀 #1943: Make 'releases' and 'shared' directory names configurable from deployment target
    • 🚀 #1922: Prevents last good release from being deleted during cleanup if there are too many subsequent failed deploys
    • 0️⃣ #1930: Default to locking the version using the pessimistic version operator at the patch level.

    🛠 Fixes:

    • 🔌 #1937: Clarify error message when plugin is required in the wrong config file.
  • v3.9.1

    September 08, 2017

    v3.9.0...v3.9.1

    💥 Breaking changes:

    • None

    🛠 Fixes:

    • 🖨 #1912: Fixed an issue where questions posed by ask were not printed on certain platforms - @kminiatures
  • v3.9.0

    July 28, 2017

    v3.8.2...v3.9.0

    💥 Breaking changes:

    • None

    🆕 New features:

    • #1911: Add Capistrano::DSL#invoke! for repetetive tasks

    🛠 Fixes:

    • 🚀 #1899: Updated deploy:cleanup to continue rotating the releases and skip the invalid directory names instead of skipping the whole rotation of releases. The warning message has changed slightly due to the change of behavior.
  • v3.8.2

    June 16, 2017

    v3.8.1...v3.8.2

    💥 Breaking changes:

    • None

    Other changes:

    • 🗄 #1882: Explain where to add new Capfile lines in scm deprecation warning - @robd
  • v3.8.1

    April 21, 2017

    v3.8.0...v3.8.1

    💥 Breaking changes:

    • None

    🛠 Fixes: