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

Close #3903 Add schema_metatag module as dependency of az_seo #3909

Conversation

trackleft
Copy link
Member

@trackleft trackleft commented Nov 21, 2024

Description

Add schema_metatag module to composer.json
Retroactively install schema_metatag module on existing sites.
Set schema_metatag as a dependency of az_seo so it is installed by default.

Related issues

Closes #3903

How to test

Go to https://ba798ad1-83eb-423b-a219-b0e900cdfa18.probo.build/
Ensure that az_seo module is enabled. (Likely)
Ensure that schema_metatag is enabled.

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

  • Patch release changes
    • Bug fix
    • Accessibility, performance, or security improvement
    • Critical institutional link or brand change
    • Adding experimental module
    • Update experimental module
  • Minor release changes
    • New feature
    • Breaking or visual change to existing behavior
    • Upgrade experimental module to stable
    • Enable existing module by default or database update
    • Non-critical brand change
    • New internal API or API improvement with backwards compatibility
    • Risky or disruptive cleanup to comply with coding standards
    • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
  • Other or unknown
    • Other or unknown

Drupal core

  • Patch release changes
    • Security update
    • Patch level release (non-security bug-fix release)
    • Patch removal that's no longer necessary
  • Minor release changes
    • Major or minor level update
  • Other or unknown
    • Other or unknown

Drupal contrib projects

  • Patch release changes
    • Security update
    • Patch or minor level update
    • Add new module
    • Patch removal that's no longer necessary
  • Minor release changes
    • Major level update
  • Other or unknown
    • Other or unknown

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • My change requires release notes.

Copy link
Contributor

@mrbeiley mrbeiley left a comment

Choose a reason for hiding this comment

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

Looks good to me.

@trackleft trackleft added backport Changes to be back-ported to previous minor release branch and removed backport Changes to be back-ported to previous minor release branch labels Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment