Add HF integration dates + paper release dates to the model docs
Author: MHRDYN7
Pull request: no
Labels: name: Feature request

### Feature request

The model docs should have the dates of publication and last update of the paper mentioned. There should also be the date when this model was add to the transformers library. 

### Motivation

Since there are so many models in transformers, it is hard to realize which models are relevant and more up-to-date. Having the dates like this 

<img width="1310" height="373" alt="Image" src="https://github.com/user-attachments/assets/543cc882-5cf1-4546-a692-4f6a9ad3e3c7" />

will make it a lot easier for the people using these docs to explore model architectures and papers. It allows people to quickly see the order in which comparable papers were published and get better idea of the evolution of model architectures.  

### Your contribution

I want to help implement the pipeline that will correctly assign the correct dates related to the papers using the arxiv api. This is relatively simple if there exists a paper associated to the model. If the model's org publishes a blogpost or something then it will be a bit more complex. @stevhliu what are your thoughts? 

Comments:
Interesting idea!

I don't think dates are necessarily a good signal for a relevant model though it would help with identifying which ones are newer. We currently link all models to their paper (or blog post if not available) which have the dates on them, so I'm not sure if there is more value of adding dates directly to the model card as well.

Alright, let me share the motivation. I was going through the video models (there are only four of these) in the docs and had to go to all the paper links to figure out which are the latest ones. Seems like 3 models are from 2021 & 2022 while the latest one [V-jepa 2](https://huggingface.co/docs/transformers/model_doc/vjepa2) (2025) had no abstract and no link to it's paper. This little inconvenience can be avoided if the docs automatically add the release date, update date + abstract (if paper exists) when a new model is contributed. It's not just about the dates (which would help me personally) but other necessary metadata tags can be automatically added alongside "pytorch", "sdpa" etc. If the keyword search feature in the docs is turned into a semantic search in future, then such tags would surely help in retrieval. So, the feature request is not just about dates but more about automation and standardization.

Yeah there is a lot of work we can do on the model docs with respect to automation and standardization! We are currently in the process of standardizing the model cards to include relevant info like a link to the paper in #36979.

I agree that it would be extremely helpful though if certain metadata and infos (the tags you mentioned + an AI generated summary of the abstract) can be automatically added and would love to see what you have in mind!

Really sorry, I should have taken a closer look at issue #36979 first. Seems like the new design for model cards serves the purpose of this library really well by having more useful info about code than about general stuff. 

Now that the abstracts will be removed, it is extremely important to ensure the link to the paper/blogpost is embedded on the name of the model. On a random check I found that [CvT](https://github.com/huggingface/transformers/pull/38731/files) and [Cohere](https://github.com/huggingface/transformers/pull/37056/files) don't have their paper and blogpost respectively, after the new standardization even though those links were present earlier.

If you think the model's release date is an important standard info for very quick distinction between, say, wav2vec2-bert/ wav2vec2-conformer/ wav2vec2-phoneme, then I'll go ahead and add something like 
```
"This model was released on {release_date} and added to Hugging Face Transformers on {hf_commit_date}" 
```
after the last `</div>` tag of all the standardized model cards. In this case you may  add this string to the template in #36979. Actually, this requirement will anyway make the contributors find the paper/blogpost link to get the date and hopefully no model will be missing the links.

No worries! I think automating certain metadata would still be super nice to avoid errors like the ones you found in CvT and Cohere.

Let's add your suggestion to the top like this:

```md
This model was released on {release_date} and added to Hugging Face Transformers on {hf_commit_date}".

<div>
...
</div>

# Model name
```

Great, I will update the draft pr #39320 and also fix the missing links.