build(deps-dev): bump env-ci from 5.0.2 to 5.4.1

[dependabot]

Bumps env-ci from 5.0.2 to 5.4.1.

Release notes

Sourced from env-ci's releases.

v5.4.1

5.4.1 (2021-10-29)

Bug Fixes

• use GITHUB_REF as documented on docs.github.com/actions (#158) (0baab54)

v5.4.0

5.4.0 (2021-10-25)

Features

• Cloudflare Pages (#156) (1f504fd)

v5.3.3

5.3.3 (2021-10-20)

Bug Fixes

• deps: update dependency execa to v5 (#153) (d6cfda0)

v5.3.2

5.3.2 (2021-10-20)

Bug Fixes

• compatibility with Node 10 (#149) (55c7b44)

v5.3.1

5.3.1 (2021-10-20)

Bug Fixes

• use GITHUB_ACTIONS env variable to detect actions (1e30d6c)

v5.3.0

5.3.0 (2021-10-18)

Features

• github: set build (#128) (e9e1644)

v5.2.0

5.2.0 (2021-10-18)

... (truncated)

Commits

• 0baab54 fix: use GITHUB_REF as documented on docs.github.com/actions (#158)
• 9a8dcd4 chore(deps): update dependency xo to v0.46.3
• 1187041 chore(deps): update dependency xo to v0.46.0
• 1f504fd feat: Cloudflare Pages (#156)
• 7bca59d chore(deps): lock file maintenance (#155)
• 439b655 ci: avoid double builds
• d6cfda0 fix(deps): update dependency execa to v5 (#153)
• 55c7b44 fix: compatibility with Node 10 (#149)
• 4c372a3 test: fix tests for new GitHub detection
• 321fbe2 docs(README): adapt badges to GitHub Actions
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by semantic-release-bot, a new releaser for env-ci since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ouzibot]

@dependabot[bot]: Invalid title for the PR, the title needs to be like:

• refactor: this is a refactor commit => if using semantic-release will trigger a patch release
• fix: this is a fix commit => if using semantic-release will trigger a patch release
• feat: this is a feature commit => if using semantic-release will trigger a minor release
• major: this is a major commit => if using semantic-release will trigger a major release
• doc: this is a doc commit => if using semantic-release won't trigger a new release
• build: this is a build commit => if using semantic-release will trigger a patch release
• no-release: this is a no-release commit => won't trigger a new release

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ouzibot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
To complete the pull request process, please assign givanov after the PR has been reviewed.
You can assign the PR to them by writing /assign @givanov in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ouzibot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a ouzi-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dependabot]

Superseded by #148.