Update SamKirkland/FTP-Deploy-Action action to v4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
SamKirkland/FTP-Deploy-Action	action	major	3.1.1 → v4.3.6

---

Release Notes

SamKirkland/FTP-Deploy-Action (SamKirkland/FTP-Deploy-Action)

v4.3.6: 🚀

Compare Source

Improved error handling when removing directories during FTP operations. In certain cases, the target directory may already be unavailable (e.g., deleted, renamed, or removed by a build process). Instead of throwing an exception, the process now logs a warning informing the user that the directory could not be removed or accessed.
What's Changed

Fixing folder 550 delete action by @​konnng-dev in SamKirkland/ftp-deploy#47

v4.3.5: 🚀

Compare Source

What's Changed

• Update to node 20
• Update basic-ftp from 5.0.2 to 5.0.5
• Update actions/checkout to v4

v4.3.4: 🚀

Compare Source

What's Changed

• Update basic-ftp
• Update actions/checkout to v3
• Glob tester README link fix
• new vX.X.X tags format

v4.3.3: 🚀

Compare Source

Node Upgrade

• v4.3.3 upgrades node12 to node16. See github deprecation announcement

Documentation

• README updates

v4.3.3: 🚀

Compare Source

Node Upgrade

• v4.3.3 upgrades node12 to node16. See github deprecation announcement

Documentation

• README updates

v4.3.2: 🚀

Compare Source

Feature

• Added timeout option

v4.3.2: 🚀

Compare Source

Feature

• Added timeout option

v4.3.1: 🚀

Compare Source

Maintenance

• Upgraded basic-ftp
• Upgraded npm dependencies

Bug Fixes

• Resolves #​285 "dry-run didn't work w/ dangerous-clean-slate"
• Resolves #​229 "None of the available transfer modes work"

v4.3.1: 🚀

Compare Source

Maintenance

• Upgraded basic-ftp
• Upgraded npm dependencies

Bug Fixes

• Resolves #​285 "dry-run didn't work w/ dangerous-clean-slate"
• Resolves #​229 "None of the available transfer modes work"

v4.3.0: 🚀

Compare Source

Bug Fixes

• Resolves "550 Remove directory operation failed" #​220
• Resolves exclude defaults not working properly

v4.3.0: 🚀

Compare Source

Bug Fixes

• Resolves "550 Remove directory operation failed" #​220
• Resolves exclude defaults not working properly

v4.2.0: 🚀

Compare Source

If you are upgrading from a pervious version see the Migration Guide

Breaking changes

• The exclude format has changed, see readme for more info - Fixes #​202

v4.2.0: 🚀

Compare Source

If you are upgrading from a pervious version see the Migration Guide

Breaking changes

• The exclude format has changed, see readme for more info - Fixes #​202

v4.1.0: 🚀

Compare Source

If you are coming from version 3 see the Migration Guide

Bug Fixes

• Cert issue - Fixes #​149 and Fixes #​127
• Exceptions now bubble up - Fixes #​123
• Resolves local-dir incorrect usage - Fixes #​145

Breaking changes

• The exclude defaults have been updated. Going forward **/.git*, **/.git*/**, **/node_modules/** will be excluded
• The exclude option now matches against folders. Previously trailing / were not matched against folders
• The security option is now loose by default (this was bugged prior to v4.1.0)

v4.1.0: 🚀

Compare Source

If you are coming from version 3 see the Migration Guide

Bug Fixes

• Cert issue - Fixes #​149 and Fixes #​127
• Exceptions now bubble up - Fixes #​123
• Resolves local-dir incorrect usage - Fixes #​145

Breaking changes

• The exclude defaults have been updated. Going forward **/.git*, **/.git*/**, **/node_modules/** will be excluded
• The exclude option now matches against folders. Previously trailing / were not matched against folders
• The security option is now loose by default (this was bugged prior to v4.1.0)

v4.0.0: 🚀

Compare Source

Migration Guide

Over the past few months I've been rewriting this action with a brand new architecture that resolves some long standing issues. The new version of this library is heavily inspired by rsync. rsync is a popular application that must be run over a ssh connection, it requires the rsync binary be install on both the client and the sever. rsync provides dozens of advanced arguments that can't be supported due to protocol limitations with ftp. Version 4 attempts to emulate at a high level how rsync syncs multiple folders, however operates over the constrained ftp protocol.

Less overhead

Version 4 no longer uses docker and has faster startup times!

Improved Defaults

.git and node_modules are now ignored by default, allowing users to opt-in to their deployment instead.

Improved Error Handling

Errors are now less cryptic.

Local Testing

Testing actions in version 3 was difficult, often requiring devs to change a value and commit it without testing the change locally. You can now run test configurations using node, see readme for more info.

Minimize downtime

The deployment is now setup in a way that minimizes downtime. For example, new files can be uploaded, then existing files updated, and finally old files deleted.

Removed features 🗑️

sftp support has been removed. In hindsight this never should have been added. Users with sftp access should be using rsync over ssh. I will create a separate github action for rsync deployments (coming soon)

v4.0.0: 🚀

Compare Source

Migration Guide

Over the past few months I've been rewriting this action with a brand new architecture that resolves some long standing issues. The new version of this library is heavily inspired by rsync. rsync is a popular application that must be run over a ssh connection, it requires the rsync binary be install on both the client and the sever. rsync provides dozens of advanced arguments that can't be supported due to protocol limitations with ftp. Version 4 attempts to emulate at a high level how rsync syncs multiple folders, however operates over the constrained ftp protocol.

Less overhead

Version 4 no longer uses docker and has faster startup times!

Improved Defaults

.git and node_modules are now ignored by default, allowing users to opt-in to their deployment instead.

Improved Error Handling

Errors are now less cryptic.

Local Testing

Testing actions in version 3 was difficult, often requiring devs to change a value and commit it without testing the change locally. You can now run test configurations using node, see readme for more info.

Minimize downtime

The deployment is now setup in a way that minimizes downtime. For example, new files can be uploaded, then existing files updated, and finally old files deleted.

Removed features 🗑️

sftp support has been removed. In hindsight this never should have been added. Users with sftp access should be using rsync over ssh. I will create a separate github action for rsync deployments (coming soon)

v3.1.2: 🚀

Compare Source

Node Upgrade

• v3.1.2 upgrades node12 to node16. See github deprecation announcement

v3.1.2: 🚀

Compare Source

Node Upgrade

• v3.1.2 upgrades node12 to node16. See github deprecation announcement

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.