Skip to content

chore(deps): update bytebase/bytebase docker tag to v3.5.3 #3659

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wanghe-fit2cloud merged 2 commits into from
Apr 10, 2025
Merged

chore(deps): update bytebase/bytebase docker tag to v3.5.3 #3659

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d8f5155
chore(deps): update bytebase/bytebase docker tag to v3.5.3
renovate[bot] Apr 10, 2025
da5b6cb
Update app version [skip ci]
Apr 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 apps/bytebase/3.5.2/data.yml → apps/bytebase/3.5.3/data.yml
View file
Open in desktop
File renamed without changes.
2 changes: 1 addition & 1 deletion apps/bytebase/3.5.2/docker-compose.yml → apps/bytebase/3.5.3/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
bytebase:
image: bytebase/bytebase:3.5.2
image: bytebase/bytebase:3.5.3
container_name: ${CONTAINER_NAME}
restart: always
networks:
Copy link
Copy Markdown
Member

@wanghe-fit2cloud wanghe-fit2cloud Apr 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code difference seems to be minor changes in the version number from 3.5.2 to 3.5.3. These versions typically only include bug fixes or improvements in the application without major architectural updates. There are no irregularities, potential issues, or optimizations needed at this time; only a change in one of the service parameters (image tag).

Here's an example of how the configuration might look if there were other changes:

@@ -1,6 +1,8 @@
 services:
   bytebase:
     image: bytebase/bytebase:3.5.3
+    ports:
+      - "8000:80"
     container_name: ${CONTAINER_NAME}
     restart: always
+    environment:
+      DB_HOST: my_database_host
     networks:

Again, no special considerations required given that the update is just a patch release.

Expand Down