Skip to content

Fix project: n8n#242

Merged
mahmoud merged 2 commits into
mahmoud:masterfrom
MattTheCuber:fix-n8n
Jan 8, 2025
Merged

Fix project: n8n#242
mahmoud merged 2 commits into
mahmoud:masterfrom
MattTheCuber:fix-n8n

Conversation

@MattTheCuber

@MattTheCuber MattTheCuber commented Jan 6, 2025

Copy link
Copy Markdown
Contributor

Closes #241

n8n's tags can't be scanned automatically due to the prefix (#237 would fix). For now I hardcoded the release information.

This prompted a couple questions:

  • Should n8n even be in this list? It was 0ver for 4 years (2019-2023), and it was only added to the list 3 days ago.
  • Do you consider the last 0ver release the newest 0ver release or the one preceding the first non-0ver release? Because lot's of times I see repos publishing many 0ver releases past their first non-0ver release (for fixes/patches and such).

@mahmoud

mahmoud commented Jan 8, 2025

Copy link
Copy Markdown
Owner

Haha, I do my best to be an inclusionist, so if someone makes a PR, I tend to merge it. I'd take it up w the author of #229 ;)

But that said, if the list is getting overly long, then yeah I'd say this would be on the earlier side of the chopping block.

As for your second point, that's a great nuance. I think either one is defensible, but I'm 80:20 on last release before the first non-0ver.

@mahmoud mahmoud merged commit c4fd365 into mahmoud:master Jan 8, 2025
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.

Fix CI failing (due to n8n)

2 participants