Merge pull request #800 from publishpress/release-3.4.0

Release 3.4.0

.github/ISSUE_TEMPLATE/release-free-plugin.md

@@ -10,20 +10,20 @@ To release the Free plugin, ensure you complete all the tasks below.
 
 ### Pre-release Checklist
 
-- [ ] Create the release branch as `release-<version>` based on the development branch.
-- [ ] Review and merge all the relevant Pull Requests into the release branch.
-- [ ] Update the version number in the main plugin file and `readme.txt`, adhering to specifications from our [tech documentation](https://rambleventures.slab.com/posts/version-numbers-58nmrk4b), and commit to the release branch.
+- [ ] Create the release branch as `release-<version>` from the development branch.
+- [ ] Review and merge all relevant Pull Requests into the release branch.
+- [ ] Update the version number in the main plugin file and `readme.txt` (stable version) per [tech documentation](https://rambleventures.slab.com/posts/version-numbers-58nmrk4b), and commit to the release branch.
 - [ ] Start a dev-workspace session.
-- [ ] Run `composer update` (updating the root and lib vendors).
-- [ ] Review the updated packages. Mention any production library updates in the changelog.
-- [ ] Inspect GitHub's Dependabot warnings or Pull Requests for relevant issues. Resolve any false positives first, then fix and commit the remaining issues.
-- [ ] If necessary, build JS files for production using `composer build:js` and commit the changes.
+- [ ] Run `composer update` (updating root and lib vendors).
+- [ ] Review updated packages and mention any production library updates in the changelog.
+- [ ] Inspect GitHub’s Dependabot warnings or Pull Requests. Resolve any false positives, then fix and commit the remaining issues.
+- [ ] If needed, build JS files for production using `composer build:js` and commit changes.
+- [ ] Run `composer build:dir` to prepare the plugin for quality checks.
 - [ ] Run a WP VIP scan with `composer check:phpcs` to ensure no warnings or errors greater than 5 exist.
-- [ ] Update the `.pot` file executing `composer gen:pot` and include a note in the changelog.
-- [ ] Update the `.mo` files executing `composer gen:mo` and include a note in the changelog.
-- [ ] Especially for minor and patch releases, maintain backward compatibility for changes like renamed or moved classes, namespaces, functions, etc. Include deprecation comments and mention this in the changelog. Major releases may remove deprecated code, but always note this in the changelog.
-- [ ] Update the changelog - make sure all the changes are there with a user-friendly description and that the release date is correct.
-- [ ] Revise the changelog to include all changes with user-friendly descriptions and ensure the release date is accurate.
+- [ ] Update the language files with `composer gen:lang` and note this in the changelog.
+- [ ] For minor and patch releases, maintain backward compatibility (e.g., renamed or moved classes, namespaces, functions). Include deprecation comments and note this in the changelog. Major releases may remove deprecated code; always note this in the changelog.
+- [ ] Update the changelog in `/CHANGELOG.md` with a user-friendly description and correct release date.
+- [ ] Update the changelog in `readme.txt`, maintaining records of the last 4-5 releases only.
 - [ ] Confirm there are no uncommitted changes.
 - [ ] Build the zip package with `composer build`, creating a new package in the `./dist` directory.
 - [ ] Distribute the new package to the team for testing.

.github/ISSUE_TEMPLATE/release-pro-plugin.md

@@ -10,21 +10,23 @@ To release the Pro plugin, ensure you complete all the tasks below.
 
 ### Pre-release Checklist
 
-- [ ] Create a release branch named `release-<version>` from the development branch.
+- [ ] Create the release branch as `release-<version>` from the development branch.
 - [ ] Review and merge all relevant Pull Requests into the release branch.
-- [ ] Start a dev-workspace session.
+- [ ] Update the version number in the main plugin file and `readme.txt` (stable version) per [tech documentation](https://rambleventures.slab.com/posts/version-numbers-58nmrk4b), and commit to the release branch.
 - [ ] Verify the correct version of the free plugin is referenced in the `lib/composer.json` file. Prefer stable versions.
-- [ ] Execute `composer update` to update the root and lib vendors.
-- [ ] Review the updated packages and mention any production library updates in the changelog.
+- [ ] Start a dev-workspace session.
+- [ ] Run `composer update` (updating root and lib vendors).
+- [ ] Review updated packages and mention any production library updates in the changelog.
 - [ ] Check if all dependencies are synced from Free into the Pro plugin with `composer check:deps`. If required, merge dependencies using `composer fix:deps` and run `composer update` again.
 - [ ] Check if the free plugin uses Composer's autoload and copy the autoload definition from the free plugin to the pro plugin refactoring the relative paths, on `/lib/composer.json`. Execute `composer dumpautoload` to update the autoload files. Commit the changes.
-- [ ] Inspect GitHub's Dependabot warnings or Pull Requests for relevant issues. Resolve any false positives first, then fix and commit the remaining issues.
-- [ ] If necessary, build JS files for production using `composer build:js` and commit the changes.
+- [ ] Inspect GitHub’s Dependabot warnings or Pull Requests. Resolve any false positives, then fix and commit the remaining issues.
+- [ ] If needed, build JS files for production using `composer build:js` and commit changes.
+- [ ] Run `composer build:dir` to prepare the plugin for quality checks.
 - [ ] Run a WP VIP scan with `composer check:phpcs` to ensure no warnings or errors greater than 5 exist.
-- [ ] Update the `.pot` file executing `composer gen:pot` and include a note in the changelog.
-- [ ] Especially for minor and patch releases, maintain backward compatibility for changes like renamed or moved classes, namespaces, functions, etc. Include deprecation comments and mention this in the changelog. Major releases may remove deprecated code, but always note this in the changelog.
-- [ ] Revise the changelog to include all changes with user-friendly descriptions and ensure the release date is accurate.
-- [ ] Update the version number in the main plugin file and `readme.txt`, adhering to specifications from our [tech documentation](https://rambleventures.slab.com/posts/version-numbers-58nmrk4b), and commit to the release branch.
+- [ ] Update the language files with `composer gen:lang` and note this in the changelog.
+- [ ] For minor and patch releases, maintain backward compatibility (e.g., renamed or moved classes, namespaces, functions). Include deprecation comments and note this in the changelog. Major releases may remove deprecated code; always note this in the changelog.
+- [ ] Update the changelog in `/CHANGELOG.md` with a user-friendly description and correct release date.
+- [ ] Update the changelog in `readme.txt`, maintaining records of the last 4-5 releases only.
 - [ ] Confirm there are no uncommitted changes.
 - [ ] Build the zip package with `composer build`, creating a new package in the `./dist` directory.
 - [ ] Distribute the new package to the team for testing.

CHANGELOG.md

@@ -3,6 +3,27 @@
 The format is based on [Keep a Changelog](http://keepachangelog.com/)
 and this project adheres to [Semantic Versioning](http://semver.org/).
 
+= [3.4.0] - 20 Jun, 2024 =
+
+* ADDED: In the JS context, implemented a way to extend the future action panel using SlotFill `FutureActionPanelAfterActionField` and setting extra fields to the panel, right after the action field;
+* ADDED: Add a new filter to allow filtering the options of the future action being scheduled: `publishpressfuture_prepare_post_expiration_opts`;
+* ADDED: Add method `scheduleRecurringAction` to the `CronToWooActionSchedulerAdapter` to schedule recurring action;
+* ADDED: Add method `scheduleAsyncAction` to the `CronToWooActionSchedulerAdapter` to schedule async action;
+* ADDED: In the JS context, added the slot `FutureActionPanelTop` to the beginning of the future panel;
+* CHANGED: Added `$unique` and `$priority` arguments to the `scheduleSingleAction` method in the `CronToWooActionSchedulerAdapter` class;
+* CHANGED: Method `scheduleRecurringAction` renamed to `scheduleRecurringActionInSeconds` in the `CronToWooActionSchedulerAdapter` class;
+* CHANGED: Added argument `$clearOnlyPendingActions` to the method signature `clearScheduledAction` to the `CronInterface` interface;
+* CHANGED: Changed the method `clearScheduledAction` in the class `CronToWooActionSchedulerAdapter` adding new argument `$clearOnlyPendingActions`, allowing to remove running actions;
+* CHANGED: The plugin activation and deactivation callback functions were moved from the main file to independent files;
+* CHANGED: Change the admin menu names for clarity;
+* CHANGED: Update the promo sidebar for mentioning the Actions Workflow feature;
+* FIXED: Fix error when quick-edit data is not available, #730;
+* FIXED: Fix dependency of the enqueued scripts for the future action box. Add 'wp-i18n', 'wp-components', 'wp-url', 'wp-data', 'wp-api-fetch', 'wp-element', 'inline-edit-post', 'wp-html-entities', 'wp-plugins' as dependencies;
+* FIXED: Updated ES, FR and IT translations, #698;
+* FIXED: Redirects to the settings page after activating the plugin, #764;
+* FIXED: Fix access to the View Debug settings tab when debug is disabled;
+* FIXED: Fix the position of the "Upgrade to Pro" and "Settings" menu items in the admin bar;
+
 = [3.3.1] - 19 Mar, 2024 =
 
 * ADDED: Add validation for the date and time offset in the settings page, #683;

assets/jsx/block-editor.jsx

@@ -1,7 +1,7 @@
 import { createStore } from './data';
 import { FutureActionPanelBlockEditor } from './components';
-import { select } from '&wp.data';
-import { registerPlugin } from '&wp.plugins';
+import { select } from '@wordpress/data';
+import { registerPlugin } from '@wordpress/plugins';
 import {
     actionsSelectOptions,
     is12Hour,

assets/jsx/bulk-edit.jsx

@@ -1,7 +1,7 @@
 import { FutureActionPanelBulkEdit } from './components';
 import { createStore } from './data';
-import { createRoot } from '&wp.element';
-import { select, dispatch } from '&wp.data';
+import { createRoot } from '@wordpress/element';
+import { select, dispatch } from '@wordpress/data';
 import { inlineEditPost } from "&window";
 import {
     postTypeDefaultConfig,

assets/jsx/classic-editor.jsx

@@ -1,8 +1,8 @@
 import { FutureActionPanelClassicEditor } from './components';
 import { createStore } from './data';
 import { isGutenbergEnabled } from './utils';
-import { createRoot } from '&wp.element';
-import { select } from '&wp.data';
+import { createRoot } from '@wordpress/element';
+import { select } from '@wordpress/data';
 import {
     postType,
     isNewPost,
@@ -16,7 +16,7 @@ import {
     defaultDate,
     statusesSelectOptions
 } from "&config.classic-editor";
-import { render } from "&ReactDOM";
+import { render } from "react-dom";
 
 if (! isGutenbergEnabled()) {
     const storeName = 'publishpress-future/future-action';

assets/jsx/components/CheckboxControl.jsx

@@ -1,8 +1,8 @@
 /*
  * Copyright (c) 2023. PublishPress, All rights reserved.
  */
-import { Fragment, useState  } from "&wp.element";
-import { CheckboxControl as WPCheckboxControl } from "&wp.components";
+import { Fragment, useState  } from "@wordpress/element";
+import { CheckboxControl as WPCheckboxControl } from "@wordpress/components";
 
 export const CheckboxControl = function (props) {
     const [checked, setChecked] = useState(props.checked || false);

assets/jsx/components/DateTimePicker.jsx

@@ -1,5 +1,5 @@
 import { normalizeUnixTimeToMilliseconds } from "../time";
-import { DateTimePicker as WPDateTimePicker } from "&wp.components";
+import { DateTimePicker as WPDateTimePicker } from "@wordpress/components";
 
 
 export const DateTimePicker = ({currentDate, onChange, is12Hour, startOfWeek}) => {