Skip to content
This repository has been archived by the owner on Jun 12, 2022. It is now read-only.

Releases: tpg/attache

v0.7.10

21 Oct 14:22
Compare
Choose a tag to compare

Fixed a similar bug as the v0.7.9 release where the release ID was not passed into the script compiler correctly. Some script tags would not return the correct release path.

v0.7.9

21 Oct 13:39
Compare
Choose a tag to compare

Fixed a bug where the release ID was not passed into the script compiler correctly. Some script tags would not return the correct release path.

v0.7.8

27 Sep 10:11
d77f18d
Compare
Choose a tag to compare

Attache will now first check that an asset exists before trying to copy to the target server. I've been using a different pipeline these days, and this makes it easier to deal with the difference.

v0.7.7

01 Jul 14:58
Compare
Choose a tag to compare

Made a small update so that if a new SSH key is added, Attaché doesn't end with an error.

v0.7.6

02 Jan 07:20
Compare
Choose a tag to compare

Small dependency update to bump the Guzzle version.

v0.7.5

16 Dec 13:14
Compare
Choose a tag to compare

Moved from Travis CI to GitHub Actions. Very nice. Might investigate this a little more and see what we can do.
Otherwise, one small new addition: there is now an @artisan script tag to you don't need to do things like @php {{ @path:serve }}/artisan any more.
The new tag will refer to the artisan script in the serve directory which is useful if you need to run artisan commands against the outgoing deployment BEFORE it gets replaced. This means that @artisan will always refer to the current deployment in all hooks except after-live.

v0.7.4

30 Nov 07:00
Compare
Choose a tag to compare

Tiny update so PHP 8 is supported.

v0.7.3

16 Nov 12:57
Compare
Choose a tag to compare

Included some recent versions of dependencies so we don't get problems when the most recent version of the Laravel installer is available.

v0.7.2

14 Sep 20:26
Compare
Choose a tag to compare

A small update to include a message of the releases being purged. This is helpful when purging a large number of releases which can sometimes take a little while to complete.

v0.7.1

24 Aug 08:16
Compare
Choose a tag to compare

All processes run by the deploy and install commands have a much increased timeout now. Previously it was only 60 seconds which was easy to reach with long running deployments. The timeout has been increased to 3600 seconds now for both local and remote running tasks. This should be more than enough for any deployment task.