Skip to content

Updated Vortex to 'ffe06eb'. #325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AlexSkrypnyk wants to merge 3 commits into
base: develop
Choose a base branch
from
Open

Updated Vortex to 'ffe06eb'. #325

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3c077c3
Reconciled '.github/workflows/update-dependencies.yml' with Vortex 'f…
AlexSkrypnyk Sep 7, 2026
75aeef6
Updated Vortex version badge.
AlexSkrypnyk Sep 7, 2026
eeda747
Removed the obsolete '.vortex-manifest.json' ignore rule.
AlexSkrypnyk Sep 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/update-dependencies.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ jobs:

- name: Run Renovate
if: steps.check-requirements.outputs.should_run == 'true'
uses: renovatebot/github-action@39b914146caeff8cd512e61c8992f1d5913af85c # v46.2.5
uses: renovatebot/github-action@37beffda261423addd537c33f2d126df7f6ffbab # v46.2.6

@AlexSkrypnyk AlexSkrypnyk Sep 7, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vortex ffe06eb: drevops/vortex#3095

Routine Renovate action bump, SHA-pinned as this repo requires. This is the only consumer-facing file that genuinely changed upstream between 1.41.1 and the installed ref - git diff --name-only 1.41.1 ffe06eb4 returns 12 files and the other 11 are all under .vortex/** (installer sources, its tests and fixtures, the docs site), which never reach a consumer project.

Worth noting what is not in this hunk. The installer also proposed dropping the trailing comment from issues: write in the permissions: block a few lines above. That comment is this project's own, not template content, so it was re-applied on top of the bump rather than accepted as an update. The same re-render also proposed rolling the DB cache key in build-test-deploy.yml back from v26.8.1 to v26.8.0; that file was reverted entirely.

with:
configurationFile: renovate.json
token: ${{ secrets.RENOVATE_TOKEN }}
Expand Down
4 changes: 0 additions & 4 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,3 @@ web/themes/**/build
/docker-compose.override.yml
/.env.local
/.ahoy.local.yml

@AlexSkrypnyk AlexSkrypnyk Sep 7, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vortex ffe06eb: drevops/vortex#3096

This deletion is the consumer-side consequence of the upstream change this PR installs, so it is worth stating plainly why removing an ignore rule is safe.

The rule was added during the 1.41.1 update, when the installer wrote a .vortex-manifest.json checksum file into the project to record what it had installed. Upstream #3096 removes that mechanism: the installer now derives the previous install state at run time and writes a human-readable .logs/vortex-update.md registry instead, listing for every file both the project change an update replaced and the change the update brings. Nothing writes .vortex-manifest.json any more, and it is absent from the working tree after this run, so the rule names a file that no longer exists.

One caveat for whoever runs the next update. The fix is on Vortex main but not yet in a published release - 1.41.1 is still the latest tag, and the ahoy update-vortex wrapper defaults VORTEX_INSTALLER_URL to the major-pinned https://www.vortextemplate.com/v1/install, which still serves the 1.41.1 build. A plain ahoy update-vortex today will therefore still write .vortex-manifest.json, and with this rule gone it will surface as an untracked file rather than being ignored. Either run the update against the development installer as this PR did, or delete the stray file afterwards.

# Checksum record written by the Vortex installer. It describes one machine's
# install rather than the project, so it stays out of version control.
/.vortex-manifest.json
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Drupal 11 implementation of DrevOps Website for DrevOps

[//]: # (DO NOT REMOVE THE BADGE BELOW. IT IS USED BY VORTEX TO TRACK INTEGRATION)

[![Vortex](https://img.shields.io/badge/Vortex-1.41.1-65ACBC.svg)](https://github.com/drevops/vortex/tree/1.41.1)
[![Vortex](https://img.shields.io/badge/Vortex-ffe06eb-65ACBC.svg)](https://github.com/drevops/vortex/tree/ffe06eb)

@AlexSkrypnyk AlexSkrypnyk Sep 7, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Standard Vortex integration badge bump, tracking the installed ref.

The value is a short SHA rather than a version because the installed ref is unreleased - this PR tracks the head of Vortex main (ffe06eb4), which is two commits ahead of the 1.41.1 tag. There is a 25.11.0 release draft upstream whose body does reference both of those commits, but it is the stale CalVer draft left over from before Vortex returned to SemVer at 1.34.0, so naming the badge after it would point this project at a dead tag line.

The installer writes the full 40-character SHA here; it was shortened by hand, since a 40-character Shields.io badge is unreadable and the short form resolves the same in the GitHub tree URL.


</div>

Expand Down
Loading