Cloud integration: Deploy version release

[ethelynmatias]

Related:

• Cloud integration #2
• TangibleInc/example-plugin-with-cloud#1

---

Warning

DO NOT MERGE ON MAIN, REVIEW ONLY

@eliot-akira please do not merge it on main this will only apply for new plugins that should be uploaded on cloud.

I successfully pushed the zip on cloud. Oh the only missing the changelog details do we have that?

After Release script:

Uploaded on cloud website after release

[eliot-akira]

successfully pushed the zip on cloud

Excellent, glad to see you were able to extend the pipeline script for your purpose.

Instead of running curl in a child process, it would be more efficient to use the native Fetch API available in the JavaScript runtime. But maybe it's too much effort to convert it, like attaching a file through FormData.

We can leave that for later, I'll create an issue as reminder.

• Cloud integration: Use native fetch API instead of curl in child process #4

---

missing the changelog details

You'll need to extract the change log from the plugin's readme.txt.

For example:

== Changelog ==

= 0.1.0 =

Release Date: 2025-01-01

- Initial release

https://github.com/TangibleInc/example-plugin-with-cloud/blob/c1d6fce17d6c1dde00bd6b13f291602b4e6c6ab5/readme.txt#L20-L26

The easiest way to extract it would be to fs.readFile() the file content; split it at the keyword == Changelog ==; then split the rest into lines (or regular expression to split at version header) and gather the newest version's change log.

[eliot-akira]

By the way, what's the difference between Plugin ID and Product ID?

[ethelynmatias]

@eliot-akira

By the way, what's the difference between Plugin ID and Product ID?

The product id is the main product the plugin_id is the plugin uploads id

There can be multiple product on the plugin. Product & Variation

[eliot-akira]

There can be multiple product on the plugin

I see, that makes sense. Thanks for the explanation.

---

By the way, in the review comments I wrote above, you can click "Commit suggestion" for each one and it will create Git commits to make the change.

[ethelynmatias]

@eliot-akira resolved your suggestions here, Thank you :)

[eliot-akira]

Yeah, I see you're getting closer with the plugin change log.

From the example plugin's Actions log:

• https://github.com/TangibleInc/example-plugin-with-cloud/actions

For the latest build, in the section "After release script":

• https://github.com/TangibleInc/example-plugin-with-cloud/actions/runs/17767106323/job/50493156463

The change log is still getting the entire readme.txt. To extract the change list for the newest version only, after this line:

pipeline/after-release.ts

Line 54 in e2fde05

changelog = await fs.readFile(readmePath, 'utf8')

We can split the text by lines, and go through them to gather the specific lines we need. I'll make a code suggestion, you can see how it might work.

[ethelynmatias]

@eliot-akira can I use another changelog.txt for changelog ? coz for readme there will be installation process @ghen-arvesu

[eliot-akira]

can I use another changelog.txt for changelog?

WordPress plugins have a standard format for readme.txt, whose content is used in various places including plugin update notices. So it won't make sense to have the change log duplicated in a separate file.

• https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/

for readme there will be installation process

Could you elaborate on what this means, and how it relates to the change log?