mirror of
https://github.com/pelican-dev/panel.git
synced 2026-02-24 11:20:41 +03:00
[PR #1222] [MERGED] Update original migrations with nullable #1259
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/pelican-dev/panel/pull/1222
Author: @lancepioch
Created: 4/6/2025
Status: ✅ Merged
Merged: 4/8/2025
Merged by: @lancepioch
Base:
main← Head:lance/migs📝 Commits (1)
e01b738These have to be nullable originally📊 Changes
16 files changed (+18 additions, -18 deletions)
View changed files
📝
database/migrations/2016_08_30_213301_modify_ip_storage_method.php(+1 -1)📝
database/migrations/2016_09_04_172028_update_failed_jobs_table.php(+1 -1)📝
database/migrations/2016_09_07_163017_add_unique_identifier.php(+1 -1)📝
database/migrations/2016_09_17_194246_add_docker_image_column.php(+1 -1)📝
database/migrations/2016_10_14_164802_update_api_keys.php(+1 -1)📝
database/migrations/2017_01_12_135449_add_more_user_data.php(+1 -1)📝
database/migrations/2017_03_12_150648_MoveFunctionsFromFileToDatabase.php(+1 -1)📝
database/migrations/2017_03_31_221948_AddServerDescriptionColumn.php(+1 -1)📝
database/migrations/2017_10_02_202000_ChangeServicesToUseAMoreUniqueIdentifier.php(+1 -1)📝
database/migrations/2017_10_02_202007_ChangeToABetterUniqueServiceConfiguration.php(+2 -2)📝
database/migrations/2018_03_15_124536_add_description_to_nodes.php(+1 -1)📝
database/migrations/2020_04_10_141024_store_node_tokens_as_encrypted_value.php(+2 -2)📝
database/migrations/2021_01_10_153937_add_file_denylist_to_egg_configs.php(+1 -1)📝
database/migrations/2021_01_13_013420_add_cron_month.php(+1 -1)📝
database/migrations/2024_03_12_154408_remove_nests_table.php(+1 -1)📝
database/migrations/2024_03_14_055537_remove_locations_table.php(+1 -1)📄 Description
The recommended solution is to use migration squashing, but it's also safe to just explicitly declare these migration columns as nullable (as they were assumed to be beforehand anyways).
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.