chore(deps): update zerocracy/pages-action action to v0.0.30

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
zerocracy/pages-action	action	patch	0.0.29 -> 0.0.30

---

Release Notes

zerocracy/pages-action (zerocracy/pages-action)

v0.0.30: dimensions of terrain

Compare Source

See #​85, release log:

• fb6a1a0 by @​yegor256: #​85 license
• 75c5e2b by @​yegor256: #​85 dot
• ea7827f by @​yegor256: #​81 name

Released by Rultor 2.0-SNAPSHOT, see build log

---

Configuration

📅 Schedule: 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.

---

PR-Codex overview

This PR updates the pages-action version to 0.0.30 in the workflow file zerocracy.yml.

Detailed summary

• Updated pages-action version from 0.0.29 to 0.0.30 in the workflow file zerocracy.yml.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[github-actions]

The provided code diff shows an update to the version of an external action being used in a GitHub Actions workflow. Specifically, zerocracy/pages-action has been updated from version 0.0.29 to 0.0.30. Here are some potential points of confusion or irregularity:

1. Version Change: It's not inherently confusing or irregular, but one should be aware whenever versions of dependencies are changed. This change could introduce unexpected behavior if there are breaking changes or bugs in the new version (0.0.30).

2. Reuse of factbase: factbase: objectionary.fb is specified two times. Once before the - uses: zerocracy/[email protected] and then within the with: section. If this is intentional (like setting up a default factbase and then overwriting it for a particular action), it's fine. However, it might cause confusion as to why it's placed there twice.

3. Absence of Context: Without complete context, i.e., without knowing what other jobs or steps are part of this workflow, it's difficult to identify any wider-scale confusions or possible impacts.

In summary, this change seems straightforward and doesn't appear to have any obvious errors. Still, a full understanding would require knowledge of the specific capabilities of the version 0.0.30 of zerocracy/pages-action and the overall context of the workflow.