927 Commits

Author SHA1 Message Date
daf888dbf5 ci: ignore SECURITY.md changes 2025-07-17 13:56:34 +10:00
42702aa3d2 README - remove former Docker LIbrary Offical Images CI status 2025-07-17 13:53:05 +10:00
684edef2ea handle $ in password 2025-06-17 07:47:26 +10:00
eaf65f5053 Make 10.6 for jammy 2025-06-12 19:02:30 +10:00
bb5c0259bc main-ubi version update to 12.1.0 for mariadb-operator parsing 2025-06-12 11:19:15 +10:00
99148cc6f2 12.1 as new development release series 2025-06-12 11:13:29 +10:00
9e455daf9c remove version hacks 2025-06-12 11:12:53 +10:00
4c5048803b 11.8 to RC status
11.7 out of the versions.json
2025-06-11 07:48:21 +10:00
bc72d89291 focal EOL for 10.5/10.6 2025-06-10 09:22:06 +10:00
e9903b927e 11.8 GA + 12.0 rc - 11.7 (EOL) 2025-06-10 09:05:38 +10:00
53c54d1fe0 ci: bashbrew version bump to 0.1.13 2025-05-22 09:50:58 +10:00
08f5e83577 correct versions.json milestone 2025-05-22 09:37:52 +10:00
a272347802 10.11.13 and 11.4.7 re-release 2025-05-22 09:31:53 +10:00
9bc98d6905 Add 10.6-jammy release
To satisfy #553

Adjust update.sh and generate-stackbrew-library.sh to address the
temporary added distro.

Expected action for next release once Ubuntu 20.04 is EOL:
* remove 10.6-jammy directory
* adjust update.sh at top to have 10.6 = jammy for $suites.
* rest is per usual
2025-05-22 09:24:37 +10:00
c5669903a1 Stable 2025 Q1 updates 2025-05-09 08:37:00 +10:00
87a043a031 main -> 12.0 for mariadb-operator 2025-02-27 17:24:00 +11:00
91ba0cc702 Remove 11.6 -eol 2025-02-14 17:55:09 +11:00
8534470197 11.7.2 Stable
With a few manual hacks on version.
2025-02-14 17:55:09 +11:00
2d51039177 11.8.1 2025-02-14 17:55:09 +11:00
17518aee23 11.8 added 2025-02-13 12:38:09 +11:00
3bfeae408b 2025 Q1 Maintaince release version bump
10.5.28, 10.6.21, 10.11.11, and 11.4.5 releases
2025-02-06 08:06:18 +11:00
8bcc1d52b0 ci: mariadb operator - use ubi workflow 2025-02-05 14:53:31 +11:00
326511ac71 ubi: syntax fix missing ; 2025-02-05 14:52:28 +11:00
6184a4b8e3 Merge branch 'master' into next 2025-02-05 14:50:37 +11:00
a20211c3ed 11.6 release status is known 2025-02-05 14:34:46 +11:00
3718532788 version: remove duplicate 11.4 entry 2025-02-05 14:31:26 +11:00
0a374b1829 11.2 EOL 2025-02-05 14:31:26 +11:00
38dfbc5997 MariaDB 2025 Q1 maintence release
For 10.5, 10.6, 10.11 and 11.4
2025-02-05 14:31:26 +11:00
e7aeffc4d8 ubi: util-linux-core was missing
As highlighted in #630 a healthcheck.sh --mariadbuprade test
will use flock that is provided by util-linux-core on ubi systems.
2025-02-05 14:28:18 +11:00
a6b360fc45 11.7 release 2024-11-25 09:03:41 +11:00
59dc031f52 11.8 is development version 2024-11-25 08:47:48 +11:00
ed58e853e1 temp; update.sh bump to 11.6.2 ahead of downloads api 2024-11-22 08:43:46 +11:00
292b81d08e Update to 11.6.2 (stable) 2024-11-22 08:43:46 +11:00
08333b900b Revert "Add 11.5 back temporarly"
This reverts commit 85df6a9f3d.
2024-11-22 08:43:46 +11:00
f9c5ee5a9f Reapply "11.5 EOL"
This reverts commit 48de289b90.
2024-11-22 08:43:46 +11:00
07e42ed9b5 version.json - hack to Stable/STS for 11.5 2024-11-15 09:44:09 +11:00
58570c6f19 TEMP hack to make supportType/ReleaseStatus=Unknown as stable for 11.5
This is because its removed in download, but we still need to have
latest as 11.5 otherwise users will go back a version.
2024-11-15 09:39:34 +11:00
85df6a9f3d Add 11.5 back temporarly 2024-11-15 09:30:36 +11:00
48de289b90 Revert "11.5 EOL"
This reverts commit e4156145dd.
2024-11-15 09:29:01 +11:00
6425213505 2024Q4 part 1 release 2024-11-05 07:52:12 +11:00
c1fd2c419f update.sh - handle trailing / in path 2024-11-04 12:50:49 +11:00
e4156145dd 11.5 EOL 2024-11-04 12:50:49 +11:00
12c877197f Replication fix - updates for 11.6 2024-11-04 12:50:49 +11:00
4540d62515 healthcheck.sh add --no-connect option
There is an implicit --connect option in healthcheck
so that a normal use can be sure MariaDB is running
on a tcp socket.

There is a case in /docker-entrypoint-initdb.d where
its desirable to perform healthchecks for components
without a --connect. In this case, use --no-connect
in the healthcheck to avoid an implicit --connect test.
2024-11-04 12:50:49 +11:00
70d5dbb805 MDEV-34943 Disable replication start on initialization
START REPLIA was issued during initializing which mean that
even before /docker-entrypoint/initdb.d there was initializtion
going on.

Entrypoints that needed data initialzation didn't complete with
this nicely. Also if there wasn't any initialization there
would be little time for the replication to acheive anything
before being shutdown ready for the final start.

Moved --skip-slave-start to the default docker_temp_server_start
implementation.

Technically this is a compaibility break that is likely to be
of significants if:
* /docker-entrypoint/initdb.d contains a script waiting
  for replication to catch up.

The recitifcation to the previous behaviour is:
/docker-entrypoint/initdb.d contains a SQL to START REPLICA.
Recommend also having another script that is:

until healthcheck.sh --replication_io \
                     --replication_sql \
                     --replication_seconds_behind_master=0 \
                     --replication
                     --no-connect;
do
  sleep 1
done

Closes #614
2024-11-04 12:50:49 +11:00
5141284394 main: 11.7 currently 2024-11-04 12:50:49 +11:00
e47764f0a3 11.1 EOL 2024-11-04 12:50:49 +11:00
d8668a590a test: break config file 2024-11-04 12:50:49 +11:00
376c7ec713 revert b34b76eb88 version fix 2024-11-04 12:50:49 +11:00
407dfffbf1 partial revert on 0cb4378923 (releaseStatus hack) 2024-11-04 12:50:49 +11:00