WEBVTT

00:00.180 --> 00:05.310
With helm, we mentioned about versioning and is one last thing I wanted to mention when it came to

00:05.310 --> 00:08.340
dependencies is that we can specify versions.

00:08.850 --> 00:15.870
So I'm using something like a tool B or some people affectionately refer to as the squiggly line.

00:16.050 --> 00:20.120
Helme includes different options for versioning when it comes to the dependencies.

00:20.130 --> 00:23.100
So all is just semantic versioning what we can do here.

00:23.140 --> 00:30.330
But this allows him to do the same from version zero point four point one to version at zero point five.

00:30.750 --> 00:33.360
Put on any version so we can build this later.

00:33.360 --> 00:36.730
And a new version came out and it's a zero point four point two.

00:36.900 --> 00:41.820
It would go ahead and pull that down, but also run Helme dependancy update to pull down that change

00:43.050 --> 00:43.650
of options.

00:43.650 --> 00:44.370
We can run as well.

00:45.360 --> 00:52.170
So put it into double quotes and we could do greater than or equal to less than.

00:53.170 --> 00:58.630
Zero point five point zero, this isn't quite advanced stuff, but it may be beneficial to what you're

00:58.630 --> 01:00.130
doing in your organization.

01:00.160 --> 01:05.240
This is some really powerful stuff and it may be quite beneficial to your organization and includes

01:05.280 --> 01:08.790
link to this as well, because some organizations may use it, some may not.

01:09.010 --> 01:12.910
But always remember the golden rule, and I always say this, especially from Riddoch, of course,

01:13.300 --> 01:20.370
is when it comes to versions nobody is using, latest is asking for a world of pain, especially if

01:20.380 --> 01:21.400
things go into production.

01:21.760 --> 01:22.750
So let's keep it in a version.

01:22.750 --> 01:23.110
It was.

01:25.130 --> 01:26.060
And stick with that.

01:26.100 --> 01:26.690
There we go.

01:26.720 --> 01:27.830
That wraps up this video.