Skip to content
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.

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

ci: Omit benchmark scope commits from changelog (no-changelog) #10618

Merged
merged 1 commit into from
Aug 30, 2024

Conversation

tomi
Copy link
Contributor

@tomi tomi commented Aug 30, 2024

Summary

Commits with scope 'benchmark' are for the benchmark suite. They shouldn't end up in the n8n app changelog.

Related PR:

n8n-io/validate-n8n-pull-request-title#7

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

Commits with scope 'benchmark' are for the benchmark suite. They shouldn't
end up in the n8n app changelog.
@n8n-assistant n8n-assistant bot added the n8n team Authored by the n8n team label Aug 30, 2024
@csuermann
Copy link
Contributor

Do any linting rules need to be adjusted as well?

Copy link
Contributor

✅ All Cypress E2E specs passed

Copy link

cypress bot commented Aug 30, 2024

n8n    Run #6684

Run Properties:  status check passed Passed #6684  •  git commit 9cf3363af1: 🌳 🖥️ browsers:node18.12.0-chrome107 🤖 tomi 🗃️ e2e/*
Project n8n
Branch Review omit-benchmark-scope-from-changelog
Run status status check passed Passed #6684
Run duration 04m 44s
Commit git commit 9cf3363af1: 🌳 🖥️ browsers:node18.12.0-chrome107 🤖 tomi 🗃️ e2e/*
Committer Tomi Turtiainen
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 1
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 421
View all changes introduced in this branch ↗︎

@csuermann
Copy link
Contributor

Do any linting rules need to be adjusted as well?

Actually, I meant these checks

@tomi
Copy link
Contributor Author

tomi commented Aug 30, 2024

Do any linting rules need to be adjusted as well?

Actually, I meant these checks

@csuermann Yes. There's a related PR for that, as mentioned in the PR description.

@tomi tomi merged commit 6119434 into master Aug 30, 2024
32 checks passed
@tomi tomi deleted the omit-benchmark-scope-from-changelog branch August 30, 2024 08:07
MiloradFilipovic added a commit that referenced this pull request Sep 2, 2024
* master:
  fix(core): Flush responses for ai streaming endpoints (#10633)
  fix: Re-enable infra provisioning and teardown (no-changelog) (#10636)
  feat(core): Execution curation (#10342)
  fix(Webhook Node): Add tests for utils (no-changelog) (#10613)
  fix: Fixes to cloud benchmarks (no-changelog) (#10634)
  test: Add JS CodeNode benchmark scenario (#10632)
  refactor(editor): Migrate `MainSidebar.vue` to composition API (no-changelog) (#10538)
  build: Fix `cli` nodemon config (#10628)
  docs: Add 'benchmark' scope to PR Title Conventions documentation (#10624)
  ci: Fixes to benchmarks in cloud (#10626)
  test(editor): Increase test coverage for users settings page and modal (#10623)
  fix(Wait Node): Append n8n attribution option (#10585)
  refactor(editor): Migrate `NodeSettings.vue` to composition API (#10545)
  fix(editor): Add pinned data only to manual executions in execution view (#10605)
  ci: Omit benchmark scope commits from changelog (no-changelog) (#10618)
  fix: Disable errors obfuscation (no-changelog) (#10617)
  ci: Fix script name in gh workflow (#10619)
  ci: Fix nightly image not being pushed to ghcr (#10620)
@janober
Copy link
Member

janober commented Sep 5, 2024

Got released with n8n@1.58.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
n8n team Authored by the n8n team Released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants