Removed outdated Trusted Root CA

When creating new VPNs, now the ONLY Trusted Root CA is defined as "USERTrust ECC Certification Authority". This is in conformance to the official docs at: https://wiki.upv.es/confluence/spaces/MANUALES/pages/903381153/Windows+-+VPN+con+Microsoft+Windows+11

Another "DigiCert Assured ID Root CA" used to also be trusted. This was an old selection, which used to be the main Root CA.

For a while, while transitioning to the new Root CA, both were advised to be selected. Now the older was is no longer mentioned in the docs, so we have removed it from the configuration for future VPNs created with this tool.

Documentation updates 2 - Development

This release only updates the documentation (README), adding instructions in the Development version on how to publish a new version of the tool.

Refer to the release's notes for v0.4.0 for more details about breaking changes betwen v0.3 and v0.4.

---

Release notes for v0.4.0 (for reference):

Now VPN or drive errors within the upv-cli tool return non-zero exit codes. This should help with scripting to differentiate between total success, program failures/errors or errors within the VPN/drive internal commands (Add-VpnConnection, rasdial, net use...).

Also, upv drive now contains new aliases:

connect : alias for mount
disconnect : alias for unmount

---

The upv command now returns the following exit codes:

0: Success

General errors:

These errors are common to all commands and indicate general issues:

1: General error (the program failed)
2: Invalid command or argument (parsing error)

Specific upv-cli errors:

These errors are specific to the upv-cli tool and typically indicate issues with VPN or drive operations:

10: Generic upv-cli error
11: VPN error
12: Drive error
13: Drive in use error (files or folders are open on the drive)

Documentation updates

This release only updates the documentation (README), fixing the Quickstart section and adding instructions for new installation options.

Refer to the release's notes for v0.4.0 for more details about breaking changes betwen v0.3 and v0.4.

---

Release notes for v0.4.0 (for reference):

Now VPN or drive errors within the upv-cli tool return non-zero exit codes. This should help with scripting to differentiate between total success, program failures/errors or errors within the VPN/drive internal commands (Add-VpnConnection, rasdial, net use...).

Also, upv drive now contains new aliases:

connect : alias for mount
disconnect : alias for unmount

---

The upv command now returns the following exit codes:

0: Success

General errors:

These errors are common to all commands and indicate general issues:

1: General error (the program failed)
2: Invalid command or argument (parsing error)

Specific upv-cli errors:

These errors are specific to the upv-cli tool and typically indicate issues with VPN or drive operations:

10: Generic upv-cli error
11: VPN error
12: Drive error
13: Drive in use error (files or folders are open on the drive)

More comprehensive exit codes, drive connect/disconnect aliases

Now VPN or drive errors within the upv-cli tool return non-zero exit codes. This should help with scripting to differentiate between total success, program failures/errors or errors within the VPN/drive internal commands (Add-VpnConnection, rasdial, net use...).

Also, upv drive now contains new aliases:

• connect : alias for mount
• disconnect : alias for unmount

---

The upv command now returns the following exit codes:

• 0: Success

General errors:

These errors are common to all commands and indicate general issues:

• 1: General error (the program failed)
• 2: Invalid command or argument (parsing error)

Specific upv-cli errors:

These errors are specific to the upv-cli tool and typically indicate issues with VPN or drive operations:

• 10: Generic upv-cli error
• 11: VPN error
• 12: Drive error
• 13: Drive in use error (files or folders are open on the drive)

Auto-completions for more shells

Breaking change to upv completions: Now it requires specifying a shell, like upv completions <SHELL>.

Now upv completions supports generating scripts for auto-completions for the following shells:

• Bash
• Elvish
• Fish
• PowerShell
• Zsh

For more information, check out the clap_complete library documentation.

Auto-completions for PowerShell

New command, upv completions, to generate a PowerShell script for auto-completions.

Now an error message is shown if trying to run this tool in an OS other than Windows.

Published to crates.io, README fixes

https://crates.io/crates/upv-cli

Initial release

First release!

Checkout the README for more info.