Skip to content

Sf/sync/upstream main - #5

Draft
fauresebast wants to merge 8 commits into
mainfrom
sf/sync/upstream-main
Draft

Sf/sync/upstream main#5
fauresebast wants to merge 8 commits into
mainfrom
sf/sync/upstream-main

Conversation

@fauresebast

Copy link
Copy Markdown
Collaborator

Adding originial repo new commits

rubiii and others added 8 commits July 6, 2026 16:00
* Autofixed issues
* Excluded Akami::WSSE::Signature
Bring akami's workflows and tooling to the savonrb standard.

* SHA-pin GitHub actions, drop GITHUB_TOKEN to read-only,
  persist-credentials: false, and add audit (bundle-audit +
  ruby-audit), zizmor and standardrb jobs
* Extend the test matrix to 3.4/4.0/truffleruby and add a
  provisional jruby-9.4.8 build
* upload coverage to Coveralls from the 3.4 build
* gem_push.yml: publish via trusted publishing
* dependabot.yml: track the github-actions ecosystem weekly
  with a 7-day cooldown
# Conflicts:
#	.github/workflows/ci.yml
#	Gemfile
#	lib/akami/wsse/verify_signature.rb
#	spec/akami/wsse/verify_signature_spec.rb
@fauresebast
fauresebast requested a review from a team as a code owner July 27, 2026 08:16
@fauresebast fauresebast self-assigned this Jul 27, 2026
@fauresebast
fauresebast marked this pull request as draft July 27, 2026 08:17
@fauresebast

Copy link
Copy Markdown
Collaborator Author

@aloist-pennylane I would like your opinion here

  1. Rubocop vs Standardrb
    Repo owners chose Standardrb over Rubocop. It introduces conflict with our pre-commit hooks
    As this fork is within Pennylane, should I follow Pennylane code style over original repository's?

  2. CI zizmor
    Owner introduced zizmor in their CI. It is not something I know, I currently commented it ((line 35 of CI.yml)
    Could help me identify if it is something we want to keep?

  3. CI Coveralls
    Same as above (line 97 of CI.yml)

Thanks!

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