V3 beta #282
Merged
V3 beta #282
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The commit adds a new workflow file for deleting workflow runs and also modifies an existing workflow file to check if a release is a pre-release. The new workflow file defines inputs for the repository, workflow, and what-if parameters. The modified workflow file includes a step to check if the release is a pre-release before continuing the workflow.
Added a new workflow that allows users to delete old workflow runs.
The commit adds the delete-old-workflow-runs action to the workflow. Inputs for repository, workflow, and what-if are required and have appropriate descriptions. Validation is added to ensure the correct input types are used.
Update the workflow to delete old workflow runs. The repository and workflow inputs are now hardcoded as "wizarrrr/wizarr" and ".github/workflows/tailwindcss.yml" respectively. The "what-if" input is set to true.
Currently translated at 100.0% (279 of 279 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/de/
Translations update from Hosted Weblate
Translations
- Change the runs-on value in beta-ci.yml to "self-hosted" in two jobs - Update the root directory in nginx-main.conf from "/data/frontend" to "/wizarr/frontend"
- Change runs-on value for build_ghcr and build_dh jobs in the beta-ci.yml GitHub Actions workflow from "self-hosted" to "ubuntu-latest" for consistency and reliability. - Update the session file and upload folder paths in the app configuration file to use the definitions from the definitions module for better maintainability. - Update the path to the latest file in the get_current_version function in the migrator module to use the LATEST_FILE definition for clarity and simplicity. - Update the path to the latest file in the get_current_version function in the software_lifecycle module to use the LATEST_FILE definition for consistency and readability. - Add new definitions to the definitions module for ROOT_DIR, LATEST_FILE, and DATABASE_DIR to improve configuration flexibility in different environments. - Update the environment variable names in the Dockerfile for wizarr-backend and wizarr to use DATABASE_DIR and LATEST_FILE for consistency with the definitions module. - Add a new environment variable LATEST_FILE to the Dockerfile for wizarr-frontend for consistency with the other Dockerfiles.
- Replace environment variable check with a direct import from the definitions file. - Update the database file path in the `db_file` variable. - Update the backup location in the `backup_location` variable. - Improvements made to code readability and maintainability.
- Moves the file logger path to refer to the correct database directory - Updates the secret key file path to use the correct database directory.
- Refactored the logging and database directory paths to use a constant from `definitions.py`. - Updated the paths in `logging_api.py`, `globals.py`, and `clear_logs.py` to use the constant. - This change improves code readability and maintainability.
…y. Update the Dockerfile for Wizarr backend to copy package files and install dependencies.
…ng dependencies The commit updates the beta-ci.yml and Dockerfile to specify the use of Node.js 18.18.2 for installing project dependencies. Previously, the actions/setup-node@v2 step did not explicitly set the required Node.js version, resulting in inconsistent dependency installations.
The commit updates the beta-ci.yml file to use Node.js version 18.18.2 for installing dependencies. This ensures consistent development and testing environment.
The .dockerignore file was modified to exclude /tmp, /dockerfiles/wizarr-backend/database, /apps/wizarr-backend/database, **/.venv, venv/, .git, .idea, .buildHelper.txt, and __pycache__ directories, as well as node_modules and Dockerfile from being included in Docker builds.
- Update beta-ci.yml to include Python and Poetry setup - Modify Dockerfile to build wizarr-ci image with updated dependencies and configurations - Add new docker-entrypoint.sh script for running Gunicorn and Nginx
- The Dockerfile for Wizarr CI has been updated to improve the build process. - Changes include setting environment variables, installing dependencies, and building the Wizarr backend and frontend. - System dependencies have been installed and the Wizarr frontend and backend are copied to their respective directories. - The Wizarr backend package is unpacked for further use.
- Update the branch triggering the workflow from 'v3-mono' to 'v3-beta' - Change the image tag from 'v3-mono' to 'v3-beta'
This commit updates the release workflow in the Docker Build and Push Release configuration. It introduces new steps to check if the release is a pre-release or if it is on the master branch. Depending on these conditions, the workflow may continue or be skipped. Additionally, the build process for GHCR and Docker Hub has been modified to include installation of dependencies using Node.js 18.18.2 and Python's Poetry package manager.
This commit adds the Membership interface, which includes properties for `created`, `id`, `token`, `email`, and `user_id`. This interface has been generated using a code generation tool.
- Adds the membership API to the list of routes in the __init__.py file in the backend/api/routes directory.
This commit adds a new file "membership_api.py" under the "api/routes" directory. The file contains API routes and operations related to membership. It defines a Flask namespace called "Membership" with a path "/membership". Within this namespace, there are three route methods: GET, POST, and DELETE. The GET route retrieves the membership status for the current user. It queries the database and returns the membership details if found, otherwise returns a 404 error. The POST route sets the membership status for the current user. It checks if the membership status exists and updates it if found, otherwise creates a new membership status. It saves the changes to the database and returns the updated membership details. The DELETE route deletes the membership status for the current user. It checks if the membership status exists and deletes it if found, otherwise returns a 404 error. These changes enable the application to handle membership-related operations through the API.
This commit adds a new column called 'tutorial' to the users table in the database. The column is a boolean field and has a default value of False. Additionally, a migration script is included to perform the necessary database alteration. The migration is completed successfully and a confirmation message is printed.
The build process has been simplified by removing unnecessary steps. The digest merging process has also been updated to merge the digests to the registry.
The version bumping step was removed from the beta-ci workflow as it is no longer necessary.
- Removed duplicate dependency installation step - Updated Node.js version to 18.18.2 - Added comments for better clarity and understanding - Consistently installed dependencies using npm
- Update version number from "3.4.3" to "3.4.2" in latest file and package.json file.
Add a new step to append "-beta" as tag suffix for beta releases in the CI workflow file. This ensures that beta versions are easily identifiable.
Previously, the beta CI workflow only included steps to login to GitHub Container Registry. This commit adds an additional step to login to Docker Hub using the docker/login-action@v3 action. The login is performed using the provided Docker Hub registry, username, and token from the secrets. This step ensures authenticated access to Docker Hub for subsequent actions in the workflow.
- Revert version from 3.4.4 to 3.4.2 in package.json and package-lock.json, in order to align version numbers.
Translations
This commit includes changes to automatically bump the version and update the latest file to match the package.json version.
This commit adds a step to clear the digests of artifacts before the build process starts. It uses a GitHub action called `geekyeggo/delete-artifact@v2`. The purpose of this change is to ensure that the build process starts with a clean state and avoids any conflicts or issues with the existing digests.
This commit adds code to create a `current_version` file and save it as an artifact. It also updates the code to copy the version from the artifact file to the `latest` file.
- Update release workflow to get the release version from the release tag. - Update package.json and latest file version to match the release tag. - Commit the changes to package.json and latest file. - Updated .hintrc to disable "axe/name-role-value" and "typescript-config/strict" hints. - Update i18n.ts to fix formatting issues. - Update Discord.vue to improve user instructions. - Update shims/gettext.d.ts to fix TypeScript declaration.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.