bwce-docker Github folder structure compatibility with different versons of BWCE release

[bibhuduttaGitHub]

Team,
we got a clone of bwce-docker repo in our Enterprise github around May 2020. We could build images for BWCE 2.5.3 & 2.5.4 and several other engg Builds that we received periodically from TIBCO.

But now , when we got the latest BWCE 2.6.0 release, we tried to build the image using the same old GitHUb bwce-docker repo, image got build successfully. But when we deploy the apps on kubernetes, we got the following error during container startup

"java.lang.NoClassDefFoundError: com/tibco/bw/encryptor/EncryptorService
at com.tibco.bwce.profile.resolver.ProfileResolverHelper.replaceProfileValues(ProfileResolverHelper.java:87)
at com.tibco.bwce.profile.resolver.DockerProfileTokenResolver.resolveTokens(DockerProfileTokenResolver.java:239)
at com.tibco.bwce.profile.resolver.DockerProfileTokenResolver.resolve(DockerProfileTokenResolver.java:37)
at com.tibco.bwce.profile.resolver.Resolver.main(Resolver.java:24)
Caused by: java.lang.ClassNotFoundException: com.tibco.bw.encryptor.EncryptorService
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 4 more".

After trying with so many different options, we thought to take the latest clone of GitHub repo "bwce-docker" . We built the image and this time, there was absolutely no container startup error. App was able to come-up fine.

The question here is:

1. Can we not take the clone once and rely on it to build our images for upcoming bwce releases?
2. Do we have to take the latest clone of bwce-docker always?
3. If we want to maintain our own repo in the enterprise, what is the recommended solution/best practices to achieve this?
4. Does the folder structures or the contents of the bwce-docker changes frequently?