Skip to content

[13.x] Add nightly workflow to verify framework install#60532

Open
jackbayliss wants to merge 1 commit into
laravel:13.xfrom
jackbayliss:13.x-skeleton-nightly
Open

[13.x] Add nightly workflow to verify framework install#60532
jackbayliss wants to merge 1 commit into
laravel:13.xfrom
jackbayliss:13.x-skeleton-nightly

Conversation

@jackbayliss

@jackbayliss jackbayliss commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Currently, there's no tests for ensuring the latest branch installs correctly which #60525 highlighted

This PR adds a nightly workflow that:

  • Creates a fresh laravel/laravel app
  • Requires laravel/framework:13.x-dev
  • Composer installs & runs php artisan about

Passing: https://github.com/jackbayliss/framework/actions/runs/27650345931
Catching a real breakage: https://github.com/jackbayliss/framework/actions/runs/27650957089/job/81774575916#step:5:492

This essentially is an attempt at catching any issues that affect installation / updating before it reaches the public

Should be fairly easy to maintain like all the other workflows.

Thought I'd give this a go to be visible to all, would rather more eyes, but I can run it myself so no drama if you don't dig it :bowtie:

Note: this currently relies on checking the workflow results, like the other nightly workflows, but you can wire them up to notifications etc if you want. Idea is for now, at least it's visible!

just one php ver is fine and reaname

comment why

match time as database nightly

Revert "prove it breaks"

This reverts commit 980dd3c.

prove it breaks

wip

wip

test
@github-actions

Copy link
Copy Markdown

Thanks for submitting a PR!

Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

@jackbayliss jackbayliss marked this pull request as ready for review June 16, 2026 22:28
@axlon

axlon commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Love this but wonder if we might want this on any commit to a release branch/master rather than nightly. That way when a PR is merged or a commit is added right before a release it would still be caught

@jackbayliss

Copy link
Copy Markdown
Contributor Author

@axlon Thanks man, yeah that's a good option, depends on what Taylor thinks I guess! I didn't want it to be too intrusive and annoying basically 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants