feat(v1.4.2): code quality + dependencies updates

⚠️ Recommended: use the v1 git tag that targets the latest stable version instead of using specific release version tags.

What's Changed

• feat(security): update of dependencies by @Steph0 in #148
• feat(151): code quality enhancements by @Steph0 in #159
• feat(152): PR pipeline by @Steph0 in #160
• build(deps): bump @actions/io from 1.1.2 to 1.1.3 by @dependabot in #149

Full Changelog: v1.3.0...v1.4.2

feat(v1.3.0): update of node + dependencies

⚠️ Recommended: use the v1 git tag that targets the latest stable version instead of using specific release version tags.

• [modified] Dependencies update
• [modified] Runs on Node16 (previously Node12)
• [modified] Documentation + test action

feat(v1.2.0): update of dependencies + documentation

⚠️ Recommended: use the v1 git tag that targets the latest stable version instead of using specific release version tags.

• [modified] npm audit fix for transitive dependencies
• [modified] tool-cache, jest, ncc, eslint
• [modified] README.md, test.event

feat(v1.1.0): Env to outputs & security updates

⚠️ Recommended: use the v1 git tag that targets the latest stable version instead of using specific release version tags.

• [added] Action now also loads configuration to outputs so that configuration can be available to other jobs
• [modified] Security updates + fix to match new @actions/github API
• [modified] Documentation

feat(v1.0.0): First features

Implementing those features:

Parameter	Required	Description	Example
repository	true	The repository ref /	repository: "Steph0/dotenv-configserver"
token	true	This should be a token with access to your repository scoped in as a secret	token: ${{ secrets.GITHUB_TOKEN }}
branch	false	The remote branch to checkout (default: main)	branch: "staging"
destination	false	The working folder to write configuration to (default 'RUNNER_TEMP')	destination: "/my/dest/folder"
directory	false	Look for file in configserver subdirectory (default '.'). Useful if your configserver hosts several config directories in it	directory: "my-app-dir"
filename	false	The config filename (default to '.env')	filename: "my-application.env"
profile	false	Profile for file (ex: 'prod' will make tool look for <filename_part>-.<filename_extension>) If empty, won't apply.	profile: "prod" Depending on filename will make action look for file: my-application-prod.env
cleanup	false	If false, won't delete configuration files downloaded after loading to GITHUB_ENV (default: true)	cleanup: false