Skip to content

v5.0.66
Compare
Choose a tag to compare
@johnsimons johnsimons released this 01 Apr 02:29
· 50 commits to main since this release
5.0.66
a438d77
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

"Package Application for Octopus" task v4 is back

After listening to all our customers about the previous deprecation notice on this task, we are bringing it back.
We understand changing existing pipelines is difficult. Thank you for the amazing feedback.

We are still displaying a warning about its usage but hopefully not as scary as before.

##[warning]This task is supported, but it no longer actively maintained.
It was originally created for the Octopus CLI when Octopus Deploy only supported NuGet packages.
It is recommended to migrate to the built-in 'Archive Files' task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/archive-files).
Alternatively, if NuGet package metadata is required, consider using the 'NuGet' task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/nuget) or the 'dotnet pack' task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli).

Support wildcards in OctoInstaller task

As part of the v5 release, we've removed the option of specifying latest for the OctopusCli installer task as its version.
We are "kind of" bringing it back but with a lot more options.
So you can now specify the following formats:

  • 8.* => Install latest in major version;
  • 7.3.* => Install latest in major and minor version;
  • 8.0.1 => Install exact version;
  • * => Install whatever is latest;

To migrate from latest, just replace it with *.

Assets 2
Loading