Schema redirect for wp-env.json

@ajlende requested via Slack: https://wordpress.slack.com/archives/C02QB8GMM/p1718649686552709

I need to add a new schemas.wp.org redirect for the wp-env.json file added in https://github.com/WordPress/gutenberg/pull/36276. I don’t have access to add the systems request like was done for Add redirect for Font Collection JSON schema. So I hope this is the right place to ask for help; I couldn’t find a channel for systems.

I’m making an assumption here; but it appears the expected format is:

https://schemas.wp.org/trunk/wp-env.json => https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/wp-env.json

#redirect #prio1

Reprovision dd32.dev wporg Sandbox

This request has been withdrawn pending a break in work.

As per previous posts [1], can I get my sandbox reprovisioned for VSCode?

I’ve backed up my customisations. (please note: I’m doing this at the end of each work day, just wipe the box when time comes, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me via slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. if online)

Please enable sudo switch-php.sh

#prio1 #sandbox

Delete 6.6 git branches

Today r57779-core accidentally created branches/6.6 when the intention was to create branches/6.5, this has been cleaned up in develop.svn and core.svn, but that doesn’t sync through to develop.git & core.git.

Thankfully it appears that the git sync has continued to operate without issues.

Could the following branch please be deleted from the git mirrors?

$ git remote -v
origin  git://develop.git.wordpress.org/ (fetch)
$ git branch -r | grep 6.6
  origin/6.6

$ git remote -v
origin  git://core.git.wordpress.org/ (fetch)
$ git branch -r | grep 6.6
  origin/6.6

The branch on Github should automatically be removed when it’s removed from the source repo.

FYI @davidbaumwald

#git #core #prio1

Add redirect for Google Fonts JSON file

We are currently hosting the Google Fonts JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. file for the new Font Library feature on the wordpress.org CDN. In order to work around the caching issues with the wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ CDN, would it be possible to create a redirect from a specific fonts wordpress.org subdomain to a JSON file hosted on the wordpress.org CDN?

This would allow the Google Fonts JSON file to be updated without the need to invalidate CDN cache.

For example, https://fonts.wp.org/6.5/google-fonts.json would point to => https://s.w.org/images/fonts/17.7/collections/google-fonts-with-preview.json. Then, if needed, the same URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org could be updated to point to a different GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ version of the file, e.g. https://s.w.org/images/fonts/17.8/collections/google-fonts-with-preview.json.

#prio1

Reprovision wp.org Sandbox for VS Code 1.86

Same issue as: https://make.wordpress.org/systems/2024/02/07/reprovisioned-sandbox-for-vs-code-1-86/

I want to run VSCode 1.86 and the newest versions of wordpress/scripts which currently throw:

Warning: Missing GLIBCXX >= 3.4.25! from /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.22
Warning: Missing GLIBC >= 2.28! from /lib/x86_64-linux-gnu/libc-2.24.so

I’ve deleted everything of meaning from the sandbox. Feel free to reprovision as soon as you are ready.

Thanks.

#prio1 #sandbox

[Edit Feb 27] Flipped this to #prio1 as I would ideally have it in place before WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. on March 7 since I’m a table lead.

Reprovisioned Sandbox for VS Code 1.86

I’m unable to use VS Code with Remote SSHSSH Secure SHell - a protocol for securely connecting to a remote system in addition to or in place of a password. to access my sandbox (adamwood.dev.ord.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/) with the new 1.86 version due to updated requirements, namely Linux distributions based on glibc 2.28 or later, and glibcxx 3.4.25 or later, such as Debian 10, RHEL 8, or Ubuntu 20.04.

As a workaround I have installed 1.85 and disabled updates as suggested, but this obviously isn’t satisfactory long term.

I understand it’s possible to have my sandbox reprovisioned to meet these requirements. I have backed up my customisations, so I’d like to request that you go ahead with this please.

#prio1 #sandbox

Add redirect for Font Collection JSON schema

I would like to request a new JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. schema file redirect, in line with theme.json and block.json, as discussed in this post.

As part of the new Font Library, there is a new JSON schema for defining font collections. There is more information in this PR.

The new redirect would be for:

https://schemas.wp.org/trunk/font-collection.json => https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/font-collection.json

This should be similar to how the theme.json and block.json redirects have been set up.

Thank you!

#prio1

Email rejected as ‘high probability of spam’

There’s been multiple reports over the last few weeks of emails from Gsuite being rejected due to the below details, I’ve been unable to verify it from a gsuite account.

The response from the remote server was:
554 5.7.1 High probability of spam

Here’s one example of it, including the full email headers of the rejection:
https://wordpress.slack.com/archives/C02QB8GMM/p1704295191477689

#email #prio1

Help Scout DKIM update

Hi, we got the following email from Help Scout. I’m not sure if it applies to both of our instances, or only one of them. The records need to be updated by October 16th.

As of October 16th, 2023 we will no longer be relying on SPF authentication tied to your domain when using Help Scout servers to send email as your custom email address. We are moving to a method with a focus on DKIM instead, to both modernize our infrastructure and align with industry best practices.

You’re receiving this message because your domain(s) currently has a DMARC record set to p=reject, but does not have the CNAME records to allow DKIM authentication for emails sent from Help Scout. If you do not take action before we make these changes, emails you send from Help Scout will be rejected by many email servers as they will no longer be DMARC aligned.

To continue using Help Scout servers to send emails as your domain, you’ll need to create a couple of CNAME records at the DNSDNS DNS is an acronym for Domain Name System - how you assign a human readable address to a website’s exact numeric coded location (ie. wordpress.org uses the actual IP address 198.143.164.252). provider for your domain so that recipient servers can authenticate the DKIM signature on emails you send from Help Scout.

You’ll need two CNAME records:

strong1._domainkey.[yourdomain] should point to strong1._domainkey.helpscout.net
strong2._domainkey.[yourdomain] should point to strong2._domainkey.helpscout.net

Our article Use DKIM to Help With Email Deliverability has a bit more information if you need it.

Alternatively, you may choose to set up your Help Scout mailbox to connect to your email provider to send email, instead of sending from our servers. You do not need to make changes to your DNS records if you choose to change the sending method.

Our article Outgoing Email Settings explains a bit more about the different options and has links to help with setting up the connection to your provider.

#prio1